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 |
|
jllondon
Starting Member
5 Posts |
 Posted - 2004-02-24 : 08:29:25
|
| I adopt a fairly standard approach of saving each package as a .DTS (structured storage file). I then check this into Visual Source Safe. DTS saves each version of the package, so effectively I'm repeatedly checking earlier revisions into VSS.Does anyone have any solutions to this? The only one I can come up with is to delete previous version of the package through Enterprise Manager. For a large number of packages this becomes cumbersome.Does anyone have any alternative approaches? The only one I can think of, is that given the COM structured storage file format, the COM interface may allow programatic deletion of previous versions, however I haven't done any real research into that.If anyone has any ideas / approaches, please let me know.Any suggestions are appreciated. |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-02-24 : 08:47:51
|
| I always save to files and delete the file before saving.I also script all the packages and save that so that I can look at changes in the packages and do searches for things.When I get round to it I'll post the thing I use for scripting on my web site but it's not difficult to write.You could also look at VB files.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
jllondon
Starting Member
5 Posts |
Posted - 2004-02-25 : 08:52:57
|
| Thanks for the advice NR.Additionally, does anyone have any ideas where the package version info sits in the DTS object model?Suggestions greatly appreciated. |
|
|
|
|
|
|
DTS Package Version Control in VSS