| Author |
Topic |
|
ra1814
Starting Member
6 Posts |
 Posted - 2002-08-05 : 14:40:23
|
| Is there a way in DTS to refer to the newest version of a package when calling "sub" packages from a "main" package. If I have a package that is a conglomerate of "sub" packages, if I change one of the "sub" packages I have to then go update the "main" package with the new version of the "sub" package. This is annoying. Suggestions for a solution to always reference newest version of a package or alternative way to run multiple packages from one package.I'm running SQL 2000 SP2. |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-08-05 : 14:46:21
|
| What are the "sub" packages made up of? If they only contain simple data transformations, why not combine them into one single package? You can also reuse connections and save resources. |
 |
|
|
ra1814
Starting Member
6 Posts |
Posted - 2002-08-05 : 14:51:40
|
| Lets call a "sub" package a very complicated dts package in it's own right. For my purposes we can't combine into one package. |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-08-05 : 14:54:36
|
| What about creating a job with several steps, each step calling the appropriate DTS packages in order? There's not much point in using a "master" DTS package when a regular job can do the same thing and avoid the version problem altogether. |
|
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-08-05 : 14:54:58
|
I'm pretty sure you can do what you want with the methods and properties exposed through the Packages object; however, if you think updating the "main" package by hand was annoying, you are in for a real treat  ...Jay White{0} |
|
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2002-08-05 : 15:33:58
|
| If you are executing these other packages via Execute Package Task (or even dtsrun) then by not selecting a version of that package explicitly in the main package it will always choose the latest version (this sounds like the behaviour you want). No need to change the calling package when you change the sub package.HTHJasper Smith |
|
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-08-06 : 08:54:52
|
| hmmm i typed out a reply to this and it died.Anyway, the gist of it was that, generally speaking, referring to a package by name ensures you always get the latest version while referring to a package by its UUID only gets you that specific version.Edited by - setbasedisthetruepath on 08/06/2002 09:18:36 |
|
|
|
ra1814
Starting Member
6 Posts |
Posted - 2002-08-06 : 18:17:49
|
| Thanks for the tips Jasper & setbasedisthetruepath , but it seems that the Execute Package Task in DTS package developer automatically selects the UUID of the most recent package when you specify the name. You do not have the choice of not specifying the UUID. If there is a way not to specify the UUID could you let me know how. Thnx. Robbie |
|
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2002-08-07 : 04:17:39
|
It works for for me  If I create a package called 1 and a package called 2 , both empty and save them to SQL Server. I Then modify Package 1 to add an execute package task to execute package 2 and save. If I execute package 1 then it executes package 2. If I then go into package 2 and add an export of the Northwind Customers table to Excel , save it and then execute package 1, it picks up on the fact that package 2 is now doing an export and produces the excel spreadshett. Is this not the behaviour you require ?HTHJasper Smith |
|
|
|
|
DTS: Aways refering to the newest version