Hi all,
My first forum experience at 'Forum SQL Server Integration Services'. Here we go!
I willattempt to describemy problem. In the pastI usedNonUnicodedatatypecolumnsassource andasdestination (=a kind of stagingdatabase).Due to circumstancesand support ofexoticcharacters, I haveboth source anddestinationcolumnschangedto Unicode(from varchar tonvarchar).
- In the old way (varchar to varchar) running approx. 30packagesafter eachother --> results: 38 minutesruntime
- In the new way (nvarchar to nvarchar) running approx. 30packagesafter eachother --> results: 32 minutesruntime
Can someone explain why runtime is becoming faster while using datatypes which consume more bytes of data (sizing).I was expecting that performancewould decreaseslightly.Theopposite is proven inmytest results.
Has anyone got any ideas? I was thinking that maybe SSIS handles each text source as Unicode anyway during execution and that's why there is improvement because SSIS does not have to convert twice.
Additional info, most common used components in the packages:
- I'm usinganOLEDBsourcecomponent(SQLServerNative Client10.0)
- Lookup components on a cache connection file (also changed from varchar to nvarchar)
- AndanOLEDBDestination (FastLoad)
Thanks! Any help is welcome!
Kind regards,
Mark