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.

All Forums  SQL Server 2000 Forums  SQL Server Development (2000)  Managing DTS Packages

Author  Topic  Jay99 468 Posts Posted - 2001-08-03 : 15:59:25 Somebody has to have come across this problem!! I have a dev, test and prod environs. I have a boat load of dts packages. When I move these packages from server to server (I usually open the package and save as to the destination server) there are a lot of things to hand tweak. Every connect in every package, every ExecutePackageTask with a GUID, every text source, every log to server has to be reconfigured for the destination server. I recently began writing active x tasks to go through and set the server for all of these objects. But he big question is how do I know what server I am on. My initial stab at it was to have a dynamic properties task that sets a global variable (strSever) equal to the COMPUTERNAME Environment variable. Then use the global to set all the things I used to hand tweak. That works great, if you execute the pkg from the server, but not if you execute from a workstation (it uses the COMPTERNAME of the workstation). So then I added an activex script to look at the global I just set and make sure it is one of my servers. However, I need to be able to run the pkg from my workstation, so I added in the logic that if COMPUTERNAME is not one my servers, paint a MSGBOX and ask for the server to assign to strServer. NOW, this all seems to be working for me (although I have introduced a bunch of other problems) but I am wondering if anyone has a cleaner solution. How do I just set strServer to the server the package lives on withough jumping through all those other hoops. Jay