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 |
|
bmassey
Starting Member
22 Posts |
 Posted - 2008-03-03 : 09:34:37
|
| We save our DTS packages as files and are looking into storing them in Source Control. However, the packages become very large due to DTS versioning, which Source Control can do for us. Is there a way to turn this feature off in DTS and then allow our Source Control to managing the versioning? |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-03-03 : 09:37:11
|
| what we use to do was to use save as option and physically delete packages before resaving them to avoid this... |
 |
|
|
bmassey
Starting Member
22 Posts |
Posted - 2008-03-03 : 09:42:34
|
| Thanks for the feedback!I thought about that as well but I believe that would cause separate issues with the original copy that was under Source Control. This would likely result in a brand new copy being added to Source Control each time, thus losing the ability to allow our Source Control to manage the version number and change history of the package. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-03-03 : 09:49:42
|
| Nope. it wont. What i was telling was to give save as option whil;e saving package locally & then delete the original pacakage that existed locally through the save window. Upon saving you will only have a single DTS file localy. Check this in to your source control and you will have a new version just after your current one. |
|
|
|
bmassey
Starting Member
22 Posts |
Posted - 2008-03-03 : 20:47:15
|
| I just tried this and it worked, just as you described. Thanks for your help! |
|
|
|
|
|
|
DTS Versioning - Can it be turned off?