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 |
|
skarthik4k
Starting Member
2 Posts |
 Posted - 2008-07-29 : 04:31:36
|
| Hi,I'm working on a DTS to SSIS migration project, where I have to pull records from a Sqlserver 2005 database and load an MS-Access 2000 mdb. The DTS is totally rewritten in SSIS and the package is executed successfully.But the output file(.mdb) size generated by the SSIS looks greater than that of DTS.I've compared the transformations of DTS/SSIS packages and verified that equal number of records have been transferred on both. The only changes I've implemented in SSIS against the DTS is the Data conversion from non-unicode to unicode, since my destination is MS-Access.Any help or suggestion is appreciated.Thanks much..! Regards,Karthik. |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2008-07-29 : 10:37:54
|
| unicode uses more bits for a character than non-unicodeWebfredThere are 10 types of people in the world: Those who understand binary, and those who don't... |
 |
|
|
skarthik4k
Starting Member
2 Posts |
Posted - 2008-07-30 : 00:30:15
|
| Thanks for the reply.I too suspected the Unicode conversion. To confirm this I tried a sample DTS/SSIS package that pulls records into MsAccess from Sqlserver. Both DTS and SSIS performs same transformation, but SSIS will have the unicode conversion. For my surprise the output file generated by the DTS/SSIS looks same. So I think there should be something happening apart from the unicode conversion, that increases the cost of the data pump.Regards,Karthik. |
|
|
|
|
|
|
DTS to SSIS Migration - Output file size mismatch.