Support

  3 Responses to “Support”

1. 

   Mark Gwenn says:

   January 8, 2013 at 2:03 am

   Hi all,

   My first experience at ‘SSIS Talk’. Here we go!

   I will attempt to describe my problem. In the past I used Non Unicode datatype columns as source and as destination (=a kind of staging database). Due to circumstances and support of exotic characters, I have both source and destination columns changed to Unicode (from varchar to nvarchar).
   • In the old way (varchar to varchar) running approx. 30 packages after eachother –> results: 38 minutes runtime
   • In the new way (nvarchar to nvarchar) running approx. 30 packages after eachother –> results: 32 minutes runtime

   Can someone explain why runtime is becoming faster while using datatypes which consume more bytes of data (sizing). I was expecting that performance would decrease slightly. The opposite is proven in my test 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 using an OLEDB source component (SQL Server Native Client 10.0)
   • Lookup components on a cache connection file (also changed from varchar to nvarchar)
   • And an OLEDB Destination (Fast Load)

   Thanks! Any help is welcome!
   Kind regards,
   Mark
2. 

   Mark Gwenn says:

   January 8, 2013 at 2:29 am

   Oh Oh…
   wrong place to post my question.

   I apologize for this mistake.
3. 

   W. Timothy Smith says:

   February 26, 2013 at 2:33 pm

   I am fairly new to SSIS. I have created a package that takes source files, renames them, and moves them over to an FTP site. It works fine running it from Visual Studio. I am doing a rename of files in my SSIS package and it is not looking for the files in D:\MyFiles\ like I put in creating the package when I run the package in SQL Server Agent as a job. It works fine running it from Visual Studio. But it fails and says it can not find the files in C:\WIndows\System32 when I run the job from SQL Server Agent. How do I put a path / directory in the “Set Values” fields? Or is there a better way through a Package Configuration, etc?

   Thanks for any help you can give.

   Tim

   Thanks,
   Wade