DTSX packages - have to hard code login information ?
-
I am new to SSIS DTSX package.
Question 1
I have developed some DTSX packages in my company. But when I deliver them to my client, their source & destination servers, login name & password must be different to mine.
They will execute the packages through 2005 agent job.
How can they change the above login name & password and data server names ?
Question 2
I have, eg. 200 SQL 2000 DTS packages, if I want to re-develop them with SSIS DTSX, do I need to create 200 Visual Studio Project and then generate 200 DTSX packages ?
Or are there any tools convert or migrate DTS to DTSX automatically ?
Thank you very much.
-
Q1:
You can use package configurations to save connection information and get it into variables and use those variables in the connection objects.
Q2:
I am sure there are tools that migrate the packages from 2000 to 2005. There is an in-built functionality in migrate 2K packages to 2K5 but I am not sure how well it works, cause I've never tried it.
--Ramesh
-
Dear Ramesh,
Thank you for your information.
But I need step-by-step instructions, can you tell me some web sites about what you said ?
-
onlo (1/14/2009)
Dear Ramesh,Thank you for your information.
But I need step-by-step instructions, can you tell me some web sites about what you said ?
Regarding the migration assistance tools, check DTS xChange
---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/
-
The configuration details can be altered when setting up the SQL Agent job. When creating the job step select the SQL Server Integration Services package for Type and you get all the configuration tabs to change.
Rewrite rather than convert as it is a good opportunity to review the packages, use newer methods and frequently combine old DTS jobs (often just a single dataflow) into new DTSX packages with multiple dataflows etc.
Best of all go on a course.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply