I think you multiply by a thousand and round up
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kathleené M Hunter
Sent: Wednesday, May 15, 2013 12:26 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] Convert data
Multiple what by a thousand and round up ?
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dan Ell
Sent: Wednesday, May 15, 2013 9:32 AM
To: U2 Users List
Subject: Re: [U2] Convert data from UniData to Microsoft
from UniData to Microsoft SQl server
I think you multiply by a thousand and round up
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kathleené M
Hunter
Sent: Wednesday, May 15, 2013 12:26 PM
To: u2-users
The amount of disk space the Unidata files are using
-Original Message-
From: Kathleené M Hunter kmhun...@resolutionprovider.com
To: 'U2 Users List' u2-users@listserver.u2ug.org
Sent: Wed, May 15, 2013 10:44 am
Subject: Re: [U2] Convert data from UniData to Microsoft SQl server
There are a lot of factors that will determine this.
The main thing is the data types used on the SQL side. See the following link
for size of each data type
http://msdn.microsoft.com/en-us/library/ms172424(v=sql.100).aspx
As a rule of thumb using the fixed length data types will take up more
The last one I saw was a 20MB UniData file took up 200MB in SQL Server. Having
said that, it is *highly* dependent on the nature of your data, how many
multivalued/sub-multivalued attributes there are (and how deep), as well as
what data types you select for your SQL schema.
This means there
