Save the Package as a structured file, use sourcesafe for versioning and
then just open the package in the designer from the file system. In SQL7
this is under all tasks, in SQL2000 its in the root DTS menu. Using the
structured file does have the drawback that an entire copy of the version is
saved in the file everytime so the file sizes get pretty big. As some part
of your change management process I would recomend saving the file with a
different name, once every so often, this will reset the number of internal
versions, it will also change the GUI so if you are using the guid to load
the package as sub package then you will need to be careful. You end up with
2 versioning systems but the file storage one can be redundant.
A good time to rename could be when starting a new version of the app.
--
-Euan
Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paulie" <paulhazells (AT) lineone (DOT) net> wrote
Quote:
Hi,
We'd like to store our DTS packages in Sourcesafe. I understand we can
save the package as VB or Structured storage files.
Our problem is then restoring the file into the DTS Designer so that
we can make amendments.
I know versioning is available within SQL server but we prefer to keep
all objects for a given project in sourcesafe so we have a one stop
shop for change management.
Any thoughts, ideas much appreciated,
Many Thanks
Paulie |