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 |
|
SamC
White Water Yakist
3467 Posts |
 Posted - 2003-07-29 : 18:43:10
|
I thought about posting this under "Import/Export (DTS)", but I thought that forum was more for, well, importing and exporting.I confess, it's easy for me to just post whatever in "Developer". This is my group of choice.  Although this could be a good "General SQL server" topic.I've almost run out of keystrokes, here's my question...Our DTS packages use ADO, and the connection string is hardcoded in the package. The package is protected by the owner's password, but is there any technique available (e.g. application variables) that can be used to keep the connection string elsewhere, and retrieve it in the DTS code?Sam |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-07-29 : 19:43:05
|
| You can put it in the registry and use the VBScript registry functions to read it. Be advised that the VBS registry functions only work with certain registry keys, you can't access the entire registry with them.You could also put it in a table and use ADO to retrieve it in an ActiveX task. Or store it in a file somewhere and use a FileSystemObject to read it. |
 |
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2003-07-29 : 21:58:02
|
| Hi Rob and thanks.I guess any of those solutions make it harder, but keeping a strong password is probably my best bet.Sam |
|
|
|
|
|
|
DTS packages, Security, ADO and kitchen sinks