![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Is there some way I can get the "father"-package to automatically detect changes in the "son"-package and update the link ? When changin something i have to open the father-package and point to the son-package again. And another thing ... what are the pro's and con's of saving packages to sql-server og as structurede storage files - are the latter only for transportation ? \Michael Vardinghus |
#3
| |||
| |||
|
|
It sounds as though you are having problems with versioning of the packages. This can be asily fixed/Worked around by doing this Make the Execute Package Task name dependent only (http://www.sqldts.com/default.aspx?216) Saving the packages in SQL Server means you can back up the packages as part of your backup routine. -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Michael Vardinghus" <mivar (AT) wmdata (DOT) dk> wrote in message news:eLFNFJkGEHA.684 (AT) tk2msftngp13 (DOT) phx.gbl... Is there some way I can get the "father"-package to automatically detect changes in the "son"-package and update the link ? When changin something i have to open the father-package and point to the son-package again. And another thing ... what are the pro's and con's of saving packages to sql-server og as structurede storage files - are the latter only for transportation ? \Michael Vardinghus |
![]() |
| Thread Tools | |
| Display Modes | |
| |