Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
pearsont74
Starting Member
27 Posts |
 Posted - 2007-02-01 : 11:50:58
|
| We do monthly imports to a db and the size of the access db is about 6 gigs but i noticed with this recent import that the sql db is like 14gigs?? we truncate the tables then run the import wizard...should i do something to shrink the sql db after teh truncate and before the import cause it seems like the size doubled. |
|
|
snSQL
Master Smack Fu Yak Hacker
1837 Posts |
Posted - 2007-02-02 : 12:59:11
|
| What is 14GB, the database files/s or the database plus the log files? If the log file is most of that space then you just need to truncate the log (with or without backup depending on your needs). The database files shouldn't be dramatically larger unless you are using different data types, for example Access uses a compression mechanism with Unicode character data and SQL Server does not, so if your character columns in SQL Server are all nchar, nvarchar, and ntext then the character data in SQL Server could be taking up twice as much space as the same data in Access. |
 |
|
|
|
|
|
Import from access db