Version Controlling DTS ( outside of the Db )
-
Hi,
Does anyone have an effective solution to Version controlling DTS packages outside of the msdb Db ?.
Currently our DTS packages are version controlled by SqlServer. We have been requested to version control our packages outside of the Db ( so that all application code, stored procs, DTS packages etc etc are kept in one central location dictated by our project office ). Can anyone suggest how this is best achieved?, or what is considered the best practice for DTS packages?, i.e do we generate VB versions of our DTS packages & put these in our source control tool or is there another more efficient/secure way of achieving this??
Thanks in advance for your ideas/solutions.
j
-
If you save your DTS files as .dts file (structured storage files), they still retain the previous versions.
Mind you the size of the file does get larger each time, as it is holding more data
Steven
-
As steven_white40 has suggested, you can save your packages as structured storage files. When the file is created for the first time it only saves the latest version of the package. Subsequent saves to the same file add versions to the file which will increase the size. The only way to remove the versions from the file is to save the package back to the server, remove the versions as normal and then save to a new file. Whenever you have a different version of the packages to "release", use a different filename.
However, if your project office wants to be able to do version comparissons and the like, you'll be better served by saving the packages as VB code.
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply