DTS: Problems calling packages from package.

(SQL Server 2000, SP3a)
Hello all!
I have a DTS package, that I'll call "A", which calls another package "B". In A's Global
Variable (GV) space, I'm defining the following variables:
SourceServer
SourceDatabase
SourceUser
SourcePassword
DestinationServer
DestinationDatabase
DestinationUser
DestinationPassword
I also define these same GVs in B.
I have A define the values for the GVs and I believe that they should "propagate" to B by
placing these variables in the "Outer Package Global Variables" tab.
However, when I try to change a value from A, it's like B "remembers" the last successful
value that was used (it's not picking up the changed value).
Am I doing something wrong with respect to GVs and packages calling other packages?
Thanks!
John PetersonJohn
I think you will be better to put the question to DTS.newsgroup and also
look at www.sqldts.com .
Personally , I have been calling DTS Package from stored procedure which is
accepted a parameter for GV.
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:OSDjL$ETEHA.2480@.TK2MSFTNGP10.phx.gbl...
> (SQL Server 2000, SP3a)
> Hello all!
> I have a DTS package, that I'll call "A", which calls another package "B".
In A's Global
> Variable (GV) space, I'm defining the following variables:
> SourceServer
> SourceDatabase
> SourceUser
> SourcePassword
> DestinationServer
> DestinationDatabase
> DestinationUser
> DestinationPassword
> I also define these same GVs in B.
> I have A define the values for the GVs and I believe that they should
"propagate" to B by
> placing these variables in the "Outer Package Global Variables" tab.
> However, when I try to change a value from A, it's like B "remembers" the
last successful
> value that was used (it's not picking up the changed value).
> Am I doing something wrong with respect to GVs and packages calling other
packages?
> Thanks!
> John Peterson
>|||Thanks Uri...however, it *seems* like it's not working correctly in my case. :-(
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:O3NZtGFTEHA.2944@.tk2msftngp13.phx.gbl...
> John
> I think you will be better to put the question to DTS.newsgroup and also
> look at www.sqldts.com .
> Personally , I have been calling DTS Package from stored procedure which is
> accepted a parameter for GV.
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:OSDjL$ETEHA.2480@.TK2MSFTNGP10.phx.gbl...
> > (SQL Server 2000, SP3a)
> >
> > Hello all!
> >
> > I have a DTS package, that I'll call "A", which calls another package "B".
> In A's Global
> > Variable (GV) space, I'm defining the following variables:
> >
> > SourceServer
> > SourceDatabase
> > SourceUser
> > SourcePassword
> > DestinationServer
> > DestinationDatabase
> > DestinationUser
> > DestinationPassword
> >
> > I also define these same GVs in B.
> >
> > I have A define the values for the GVs and I believe that they should
> "propagate" to B by
> > placing these variables in the "Outer Package Global Variables" tab.
> >
> > However, when I try to change a value from A, it's like B "remembers" the
> last successful
> > value that was used (it's not picking up the changed value).
> >
> > Am I doing something wrong with respect to GVs and packages calling other
> packages?
> >
> > Thanks!
> >
> > John Peterson
> >
> >
>|||A better question might be, what exactly do the two tabs do? That is, if I want to
propagate my out (caller) package's GVs to the inner (callee), do I do that from the Outer
Package tab? Or should that be done from the Inner Package tab?
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:eyt8UOFTEHA.2692@.TK2MSFTNGP09.phx.gbl...
> Thanks Uri...however, it *seems* like it's not working correctly in my case. :-(
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:O3NZtGFTEHA.2944@.tk2msftngp13.phx.gbl...
> > John
> > I think you will be better to put the question to DTS.newsgroup and also
> > look at www.sqldts.com .
> >
> > Personally , I have been calling DTS Package from stored procedure which is
> > accepted a parameter for GV.
> >
> >
> > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > news:OSDjL$ETEHA.2480@.TK2MSFTNGP10.phx.gbl...
> > > (SQL Server 2000, SP3a)
> > >
> > > Hello all!
> > >
> > > I have a DTS package, that I'll call "A", which calls another package "B".
> > In A's Global
> > > Variable (GV) space, I'm defining the following variables:
> > >
> > > SourceServer
> > > SourceDatabase
> > > SourceUser
> > > SourcePassword
> > > DestinationServer
> > > DestinationDatabase
> > > DestinationUser
> > > DestinationPassword
> > >
> > > I also define these same GVs in B.
> > >
> > > I have A define the values for the GVs and I believe that they should
> > "propagate" to B by
> > > placing these variables in the "Outer Package Global Variables" tab.
> > >
> > > However, when I try to change a value from A, it's like B "remembers" the
> > last successful
> > > value that was used (it's not picking up the changed value).
> > >
> > > Am I doing something wrong with respect to GVs and packages calling other
> > packages?
> > >
> > > Thanks!
> > >
> > > John Peterson
> > >
> > >
> >
> >
>|||From this article: http://www.winnetmag.com/SQLServer/Article/ArticleID/19747/19747.html
<Quote>
Inside the Execute Package task, you can easily pass global variables to the child
package, as Figure 1 shows. If you click the Inner Package Global Variables tab in the
Execute Package task, DTS scans the child package for any global variables that it
expects, and you can set them to your own values. Inner global variables let you set the
global variables for the child package from the Execute Package task. Inner global
variables are useful when you're calling auditing packages and you want to pass to the
child package certain errors based on events in the parent package. Outer global variables
send global variables from the parent package to the child package. If a global variable
exists in the child package, DTS updates the child's global variable to the parent's
value. If the global variable doesn't exist in the child package, DTS creates it.
</Quote>
It would *seem* that my understanding of this is accurate. Though, clearly I'm still
doing something wrong...
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:OvKJxQFTEHA.2692@.TK2MSFTNGP09.phx.gbl...
> A better question might be, what exactly do the two tabs do? That is, if I want to
> propagate my out (caller) package's GVs to the inner (callee), do I do that from the
Outer
> Package tab? Or should that be done from the Inner Package tab?
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:eyt8UOFTEHA.2692@.TK2MSFTNGP09.phx.gbl...
> > Thanks Uri...however, it *seems* like it's not working correctly in my case. :-(
> >
> >
> > "Uri Dimant" <urid@.iscar.co.il> wrote in message
> > news:O3NZtGFTEHA.2944@.tk2msftngp13.phx.gbl...
> > > John
> > > I think you will be better to put the question to DTS.newsgroup and also
> > > look at www.sqldts.com .
> > >
> > > Personally , I have been calling DTS Package from stored procedure which is
> > > accepted a parameter for GV.
> > >
> > >
> > > "John Peterson" <j0hnp@.comcast.net> wrote in message
> > > news:OSDjL$ETEHA.2480@.TK2MSFTNGP10.phx.gbl...
> > > > (SQL Server 2000, SP3a)
> > > >
> > > > Hello all!
> > > >
> > > > I have a DTS package, that I'll call "A", which calls another package "B".
> > > In A's Global
> > > > Variable (GV) space, I'm defining the following variables:
> > > >
> > > > SourceServer
> > > > SourceDatabase
> > > > SourceUser
> > > > SourcePassword
> > > > DestinationServer
> > > > DestinationDatabase
> > > > DestinationUser
> > > > DestinationPassword
> > > >
> > > > I also define these same GVs in B.
> > > >
> > > > I have A define the values for the GVs and I believe that they should
> > > "propagate" to B by
> > > > placing these variables in the "Outer Package Global Variables" tab.
> > > >
> > > > However, when I try to change a value from A, it's like B "remembers" the
> > > last successful
> > > > value that was used (it's not picking up the changed value).
> > > >
> > > > Am I doing something wrong with respect to GVs and packages calling other
> > > packages?
> > > >
> > > > Thanks!
> > > >
> > > > John Peterson
> > > >
> > > >
> > >
> > >
> >
> >
>