Upsizing creates large MSSQL

  • I am upgrading a .mdb to MSSQL.  The .mdb is 17MB, but the resulting MSSQL is 72MB.  Tried using both the Access Upsizing Wizard and Enterprise Manager DTS.  I have done this a number of times before, but never ran into this problem.  Any ideas what coule be going on, and how to fix it?

  • Check the table and indexes.

    If you don't use double-byte characters then replace an NVARCHAR, NCHAR, NTEXT columns with VARCHAR, CHAR, TEXT equivalents.

    If you have these columns then not only will the data-storage requirement double but indices on these columns will also take up more space.

    Personally I avoid the upsizing wizard like the plague because SQL Server is a completely different animal.

  • Well, you are right.  Everything was converted to 'N.......'.  That is certainly part of the problem.  Is there a way to force DTS not to do this, or must I edit each field?

  • The only way I can think of doing it would be to save the DTS package rather than use the "Run Immediately" option.  You could then edit the CREATE TABLE scripts.

    There must be tools out there that would script an Access database rather than try to blast the thing into SQL.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply