![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello, All! I can take these steps: 1. Load package. Global variables contains some vars. 2. Run package. At run time new variables added by custom task. 3. Package completed. Global variables list EMPTY. There is no any variable - not existed at point 1, not added at point 2. After last step I make dump of all GV to disk - GV are OK. So, variables exists at runtime. My custom task doesn't contain code to drop variable. Only new variables added. I can't find description about GV scopes. Is there some issues? With best regards, Alexander Sinitsin. E-mail: al_sin[dog]ukr.net |
#3
| |||
| |||
|
|
Hello, All! I can take these steps: 1. Load package. Global variables contains some vars. 2. Run package. At run time new variables added by custom task. 3. Package completed. Global variables list EMPTY. There is no any variable - not existed at point 1, not added at point 2. After last step I make dump of all GV to disk - GV are OK. So, variables exists at runtime. My custom task doesn't contain code to drop variable. Only new variables added. I can't find description about GV scopes. Is there some issues? With best regards, Alexander Sinitsin. E-mail: al_sin[dog]ukr.net |
#4
| |||
| |||
|
|
Hello, Allan! You wrote on Sat, 7 Aug 2004 09:25:43 +0100: AM> Not sure what you mean here After succesfully execution of package, all variables disappear. Even if package was saved with these variables. For example, var A always present in the package, var B added dinamically. After package execution GV list empty. My package save result of some tasks in global variables. If we start package task-by-task manually, we can see this vars. But when we run entire package, we don't see any variables. AM> If you are saying GV values are not persisted from your Execution of AM> the package to when you reopen the package then that's true. Yes, I know. Only issue - existed variables disappear too. AM> The only way to do this would be to SAVE the package back again. AM> likewise with anything you add to the package at runtime then if you AM> do not save it back then it exists for the lifetime of that run AM> only. AM> -- AM> -- AM> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) AM> www.SQLDTS.com - The site for all your DTS needs. AM> www.konesans.com - Consultancy from the people who know AM> "Alexander Sinitsin" <al_sin[dog]ukr.net> wrote in message AM> news:uFi0XuveEHA.3476 (AT) tk2msftngp13 (DOT) phx.gbl... Hello, All! I can take these steps: 1. Load package. Global variables contains some vars. 2. Run package. At run time new variables added by custom task. 3. Package completed. Global variables list EMPTY. There is no any variable - not existed at point 1, not added at point 2. After last step I make dump of all GV to disk - GV are OK. So, variables exists at runtime. My custom task doesn't contain code to drop variable. Only new variables added. I can't find description about GV scopes. Is there some issues? With best regards, Alexander Sinitsin. E-mail: al_sin[dog]ukr.net With best regards, Alexander Sinitsin. E-mail: al_sin[dog]ukr.net |
![]() |
| Thread Tools | |
| Display Modes | |
| |