Does anyone know how I can version my DTS packages so when
I track them I can just track the versions? I will use
this version number to label my directory in source safe.

Thank You
Jerry

DTS Packages are versioned by default in SQL Server. Everytime you save the
DTS package, a new version is saved in the msdb..sysdtspackages. You can see
these versions in the Enterprise Manager, by right clicking on the DTS
packages.

Another way would be to script the DTS package as a VBScript file, and check
that VB script file into VSS.
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/


"Jerry" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Vyas,
How can I read that version guid in sysdtspackages into a
normal version number that I can use in my tracking system?

How can you get the version by saving off into a VBScript
file?

Thank you for all your help

Jerry

Packages in sysdtspackages will have a new row for every time you save it
back

Name and ID will be the same
VersionID will be different as will CreateDate
When saving out to a VB module you will be saving out the latest version.

You could also save to structured Storage file and book that into Source
Control.

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


<anonymous (AT) discussions (DOT) microsoft.com> wrote

Allan,
We do save them off into a structured storage file and
that is what we take when we go out to the client site to
do a release. The problem with that is there is no
version tied to that DTS file. We want a way to make sure
that this is the correct version going out and be able to
double check it while we are out at the clients site. I
can't have the version in a GUID, I need it in a regular
format do you know if this is possible?

Thank You
Jerry

You can save the same package to the same .dts file. When you come to open
it through EM you will be asked what version you want with a Date of
modification

Also
You can retrieve information about the contents of a DTS package storage
file, which can contain multiple packages, each with multiple versions.
Create a Package2 object and then use the GetSavedPackageInfos method to
return a reference to a SavedPackageInfos collection with information about
all the package versions contained in the file.


--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Jerry" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Jyotsna,
You more then likely already have it saved using that
name. It doesn't let you overwrite it. What I do it
delete the old version out of Enterprise Manager and then
save it in SQL Server.

Thank you Jerry, for the response.

You're exactly right, I do have the package saved under the same name on the
production server. This is because it was the previously saved version. I
had considered the idea of deleting it from production and then saving the
new version, but wouldn't that impact the job associated with the package?
That is, the job would need to be re-created too, correct, since it is
referencing the old package? I was wondering if there was an
alternative/seamless solution, for a Dev/QA/Prod transition...

Thanks,
-Jyotsna


"jerry" wrote:

Jyotsna,
That will change the association in the job. What I do is
go to the new package that I just saved and right click
and go to schedule job. Once it created the job I open it
up and go to the steps tab. I then double click on the
step there and it shows me something like this :

DTSRun /~Z0x0F1FF9AE6DF2AA57D9D24EF439FCF737D4A65671C74D96 F
D0CD18E4C2757E45788FB89F76CE751E50E985CD3A9EC5E223 D48BF24C6
FCDC631CE3733FCB8C3E8F71F83B0746B7D76E05DCE030E5FC 01E21818A
B93F18D6023F9036B47BFFA430B824AF205ED6233395EC71E4 AE6B92EEB
CE8E5CB2DCEB6FD2FB1F1364F1FF6CD69FC057603D4E9BCE7C 4CFFB8EAC
2A12667D3F2

I will copy all this and then go to my original job and
past it into that job's command area. I know it's a
hassle. I hope this helps.

In message <41BED571-2AAC-456E-9E2B-B4BFEA117D66 (AT) microsoft (DOT) com>, Jyotsna
<Jyotsna (AT) discussions (DOT) microsoft.com> writes
encrypted command line, so you can use name, or at least create the
encrypted command line yourself using name only to prevent these
problems. It is very easy if you use DTSRUNUI to help.

Every time you Save As then you will get a new package ID. Every time
you Save you get a new version. Since it is the package ID clashes you
need to avoid Save As's, which means working with the same format all
the time.

You can actually play around under the covers as well. DTS packages are
stored in msdb, so you can move them between servers directly. If you
want files you can rip them out of msdb directly, and not incur the Save
As penalty. It means more work as there is no tools to do this for you,
but it may be a better option for your code migration.

Some links that may give you some more ideas-

SavePkgToFile
(http://sqldev.net/dts/SavePkgToFile.htm)

Transferring DTS Packages
(http://www.sqldts.com/default.aspx?204)

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org