![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hey, Is there a way to change in a DTS package a specific server? I explain why. I have about 140 DTS packages who collects data from an AS/400 to store in several SQL databases on a server. Now we ar migrating that server to a new one. The name of the server is different off course. I'm able to export the packages in bulk to .dts files, and I'm able to import them on the new server. Bit the server to which the import goes is still the old one. Any help is welcome, Marc |
#3
| |||
| |||
|
|
Correct Your packages should ideally read from an external source the data that it needs at runtime (Dynamic Properties Task). This makes a package more flexible. That said the only way you can do this without opening every one by hand now is to use the object model, loop through your packages, find the right connections , revalue the DataSource property of the connections, save back. "MADS" <deschepper_marc (AT) telenet (DOT) be> wrote in message news:deschepper_marc (AT) telenet (DOT) be: Hey, Is there a way to change in a DTS package a specific server? I explain why. I have about 140 DTS packages who collects data from an AS/400 to store in several SQL databases on a server. Now we ar migrating that server to a new one. The name of the server is different off course. I'm able to export the packages in bulk to .dts files, and I'm able to import them on the new server. Bit the server to which the import goes is still the old one. Any help is welcome, Marc |
#4
| |||
| |||
|
|
Thx Allan for your reply... How can I use an object model? I'm a newby on this subject. Can it be done by queries? Marc "Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote in message news:OUvOdR2CFHA.2180 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Correct Your packages should ideally read from an external source the data that it needs at runtime (Dynamic Properties Task). This makes a package more flexible. That said the only way you can do this without opening every one by hand now is to use the object model, loop through your packages, find the right connections , revalue the DataSource property of the connections, save back. "MADS" <deschepper_marc (AT) telenet (DOT) be> wrote in message news:deschepper_marc (AT) telenet (DOT) be: Hey, Is there a way to change in a DTS package a specific server? I explain why. I have about 140 DTS packages who collects data from an AS/400 to store in several SQL databases on a server. Now we ar migrating that server to a new one. The name of the server is different off course. I'm able to export the packages in bulk to .dts files, and I'm able to import them on the new server. Bit the server to which the import goes is still the old one. Any help is welcome, Marc |
#5
| |||
| |||
|
|
By queries I will presume you mean TSQL??? Technically yes you could do that but it is painful and will keep you awake at night. Have a look at this article. www.sqldts.comm/default.aspx?208 "MADS" <deschepper_marc (AT) telenet (DOT) be> wrote in message news:deschepper_marc (AT) telenet (DOT) be: Thx Allan for your reply... How can I use an object model? I'm a newby on this subject. Can it be done by queries? Marc "Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote in message news:OUvOdR2CFHA.2180 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Correct Your packages should ideally read from an external source the data that it needs at runtime (Dynamic Properties Task). This makes a package more flexible. That said the only way you can do this without opening every one by hand now is to use the object model, loop through your packages, find the right connections , revalue the DataSource property of the connections, save back. "MADS" <deschepper_marc (AT) telenet (DOT) be> wrote in message news:deschepper_marc (AT) telenet (DOT) be: Hey, Is there a way to change in a DTS package a specific server? I explain why. I have about 140 DTS packages who collects data from an AS/400 to store in several SQL databases on a server. Now we ar migrating that server to a new one. The name of the server is different off course. I'm able to export the packages in bulk to .dts files, and I'm able to import them on the new server. Bit the server to which the import goes is still the old one. Any help is welcome, Marc |
#6
| |||
| |||
|
|
By queries I will presume you mean TSQL??? Technically yes you could do that but it is painful and will keep you awake at night. Have a look at this article. www.sqldts.comm/default.aspx?208 "MADS" <deschepper_marc (AT) telenet (DOT) be> wrote in message news:deschepper_marc (AT) telenet (DOT) be: Thx Allan for your reply... How can I use an object model? I'm a newby on this subject. Can it be done by queries? Marc "Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote in message news:OUvOdR2CFHA.2180 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Correct Your packages should ideally read from an external source the data that it needs at runtime (Dynamic Properties Task). This makes a package more flexible. That said the only way you can do this without opening every one by hand now is to use the object model, loop through your packages, find the right connections , revalue the DataSource property of the connections, save back. "MADS" <deschepper_marc (AT) telenet (DOT) be> wrote in message news:deschepper_marc (AT) telenet (DOT) be: Hey, Is there a way to change in a DTS package a specific server? I explain why. I have about 140 DTS packages who collects data from an AS/400 to store in several SQL databases on a server. Now we ar migrating that server to a new one. The name of the server is different off course. I'm able to export the packages in bulk to .dts files, and I'm able to import them on the new server. Bit the server to which the import goes is still the old one. Any help is welcome, Marc |
#7
| |||
| |||
|
|
I found the error in the link...;-) Is there no easy way to "migrate" the dts packages from one server to another? MaDS "Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote in message news:eKcEin7CFHA.4052 (AT) TK2MSFTNGP15 (DOT) phx.gbl... By queries I will presume you mean TSQL??? Technically yes you could do that but it is painful and will keep you awake at night. Have a look at this article. www.sqldts.comm/default.aspx?208 "MADS" <deschepper_marc (AT) telenet (DOT) be> wrote in message news:deschepper_marc (AT) telenet (DOT) be: Thx Allan for your reply... How can I use an object model? I'm a newby on this subject. Can it be done by queries? Marc "Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote in message news:OUvOdR2CFHA.2180 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Correct Your packages should ideally read from an external source the data that it needs at runtime (Dynamic Properties Task). This makes a package more flexible. That said the only way you can do this without opening every one by hand now is to use the object model, loop through your packages, find the right connections , revalue the DataSource property of the connections, save back. "MADS" <deschepper_marc (AT) telenet (DOT) be> wrote in message news:deschepper_marc (AT) telenet (DOT) be: Hey, Is there a way to change in a DTS package a specific server? I explain why. I have about 140 DTS packages who collects data from an AS/400 to store in several SQL databases on a server. Now we ar migrating that server to a new one. The name of the server is different off course. I'm able to export the packages in bulk to .dts files, and I'm able to import them on the new server. Bit the server to which the import goes is still the old one. Any help is welcome, Marc |
#8
| |||
| |||
|
|
Transferring packages can be done like this http://www.sqldts.com/default.aspx?204 Changing the DataSources internally should be designed in from the beginning. You could use the object model to fire the packages and change the Connections' DataSource properties through that. Allan "MADS" <deschepper_marc (AT) telenet (DOT) be> wrote in message news:deschepper_marc (AT) telenet (DOT) be: I found the error in the link...;-) Is there no easy way to "migrate" the dts packages from one server to another? MaDS "Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote in message news:eKcEin7CFHA.4052 (AT) TK2MSFTNGP15 (DOT) phx.gbl... By queries I will presume you mean TSQL??? Technically yes you could do that but it is painful and will keep you awake at night. Have a look at this article. www.sqldts.comm/default.aspx?208 "MADS" <deschepper_marc (AT) telenet (DOT) be> wrote in message news:deschepper_marc (AT) telenet (DOT) be: Thx Allan for your reply... How can I use an object model? I'm a newby on this subject. Can it be done by queries? Marc "Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote in message news:OUvOdR2CFHA.2180 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Correct Your packages should ideally read from an external source the data that it needs at runtime (Dynamic Properties Task). This makes a package more flexible. That said the only way you can do this without opening every one by hand now is to use the object model, loop through your packages, find the right connections , revalue the DataSource property of the connections, save back. "MADS" <deschepper_marc (AT) telenet (DOT) be> wrote in message news:deschepper_marc (AT) telenet (DOT) be: Hey, Is there a way to change in a DTS package a specific server? I explain why. I have about 140 DTS packages who collects data from an AS/400 to store in several SQL databases on a server. Now we ar migrating that server to a new one. The name of the server is different off course. I'm able to export the packages in bulk to .dts files, and I'm able to import them on the new server. Bit the server to which the import goes is still the old one. Any help is welcome, Marc |
![]() |
| Thread Tools | |
| Display Modes | |
| |