![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We have a big DTS package that runs nightly via SQLAgent and uses several global variables. The programmer changes them via script throughout the process and assumed that the changes would be retained the next time the package was executed. Of course the programmer has now left the firm. In investigating an issue, it appears that the changed values are not making their way back to the package. So my question is, should the variable values be retained indicating that we have some failure that we need to address, or is this normal behaviour indicating that we chould create a table for values we want to be retained from run to run? Thanks in advance. |
#3
| |||
| |||
|
|
What you are seeing is the correct behavior. Global variable changes made at run time will not persist. You should think about saving them somewhere if you need them again. -- Vyas, MVP (SQL Server) http://vyaskn.tripod.com/ "Mike Singer" <nospam_mike.singer (AT) ehr (DOT) com> wrote in message news:eqpaKlnmEHA.1152 (AT) TK2MSFTNGP11 (DOT) phx.gbl... We have a big DTS package that runs nightly via SQLAgent and uses several global variables. The programmer changes them via script throughout the process and assumed that the changes would be retained the next time the package was executed. Of course the programmer has now left the firm. In investigating an issue, it appears that the changed values are not making their way back to the package. So my question is, should the variable values be retained indicating that we have some failure that we need to address, or is this normal behaviour indicating that we chould create a table for values we want to be retained from run to run? Thanks in advance. |
![]() |
| Thread Tools | |
| Display Modes | |
| |