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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-04-15 : 07:49:13
|
| Mike writes "I have a poblem with my dts because I dont want to hardcode my dts package. You see if I have a dts object in sql2000 server which have a fix source and destinations. so the problem is that when I deploy it to different servers I will have to change all my connections because of the server names and userID and passwords. what I want is a source code that transforms a flat file or an exel file to the sql database." |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-04-15 : 07:51:38
|
| If you always set your SQL Server connections to (local) instead of the server name, then you can copy it to another server with the same databases and it will work fine. The user name and passwords are a little trickier unless you're using Windows authentication, in which case you've solved that problem too.You can find out more about dynamic DTS at http://www.sqldts.com/ |
 |
|
|
ciaran
Starting Member
40 Posts |
Posted - 2005-08-17 : 09:10:53
|
| why not store the connection details in an ini file and read the properties using the dynamic task. |
|
|
|
|
|
|
dts program