 | |
Recommendations for moving a DTS package to another instance
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Recommendations for moving a DTS package to another instance -
11-14-2006
, 02:57 PM
#2
| |||
| |||
|
|
We are SS2K and need to move a package to other (remote) SS2K instances sitting behind firewalls. I read or heard somewhere, that transformations and mappings may be lost when opening a package in a different instance of SQL Server when the remote instance can't communicate with the instance on which the package was developed. Is there any value in saving the local package as a Structured Storage File and having the DBA at the remote site open the package from this file and then make the appropriate changes (like usernames and server I.P. address etc.) using disconnected edit? Is this a typical solution or are there easier/better ways of doing this? Any thoughts/suggestions would be greatly appreciated. Chris. |
#3
| |||
| |||
|
|
We are SS2K and need to move a package to other (remote) SS2K instances sitting behind firewalls. I read or heard somewhere, that transformations and mappings may be lost when opening a package in a different instance of SQL Server when the remote instance can't communicate with the instance on which the package was developed. Is there any value in saving the local package as a Structured Storage File and having the DBA at the remote site open the package from this file and then make the appropriate changes (like usernames and server I.P. address etc.) using disconnected edit? Is this a typical solution or are there easier/better ways of doing this? Any thoughts/suggestions would be greatly appreciated. Chris. |
#4
| |||
| |||
|
|
That's probably the easiest way to move a small number of packages. I move them from Dev to Prod like that all the time  -- Kevin Hill 3NF Consulting http://www.3nf-inc.com/NewsGroups.htm Real-world stuff I run across with SQL Server: http://kevin3nf.blogspot.com "Chris W" <ChrisW (AT) discussions (DOT) microsoft.com> wrote in message news:7362B0C3-C44D-4A09-BA03-C7E33009F60D (AT) microsoft (DOT) com... We are SS2K and need to move a package to other (remote) SS2K instances sitting behind firewalls. I read or heard somewhere, that transformations and mappings may be lost when opening a package in a different instance of SQL Server when the remote instance can't communicate with the instance on which the package was developed. Is there any value in saving the local package as a Structured Storage File and having the DBA at the remote site open the package from this file and then make the appropriate changes (like usernames and server I.P. address etc.) using disconnected edit? Is this a typical solution or are there easier/better ways of doing this? Any thoughts/suggestions would be greatly appreciated. Chris. |
#5
| |||
| |||
|
|
Hello Chris, You can even have a flat file export of sysdtspackages as the medium. SSFs are though convenient as well. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com We are SS2K and need to move a package to other (remote) SS2K instances sitting behind firewalls. I read or heard somewhere, that transformations and mappings may be lost when opening a package in a different instance of SQL Server when the remote instance can't communicate with the instance on which the package was developed. Is there any value in saving the local package as a Structured Storage File and having the DBA at the remote site open the package from this file and then make the appropriate changes (like usernames and server I.P. address etc.) using disconnected edit? Is this a typical solution or are there easier/better ways of doing this? Any thoughts/suggestions would be greatly appreciated. Chris. |
#6
| |||
| |||
|
|
Allan, thanks for the response...sorry to trouble you further but I have to ask what may be a dumb question. Is this as straightforward as exporting the row for my package from sysdtspackages on my "local" instance and then having someone at the "remote" instance import the data from the flat file directly into sysdtspackages on their instance? No gotchas? Will the remote DBA be able to open the package using DTS Designer after the import? Thanks again! Chris. "Allan Mitchell" wrote: Hello Chris, You can even have a flat file export of sysdtspackages as the medium. SSFs are though convenient as well. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com We are SS2K and need to move a package to other (remote) SS2K instances sitting behind firewalls. I read or heard somewhere, that transformations and mappings may be lost when opening a package in a different instance of SQL Server when the remote instance can't communicate with the instance on which the package was developed. Is there any value in saving the local package as a Structured Storage File and having the DBA at the remote site open the package from this file and then make the appropriate changes (like usernames and server I.P. address etc.) using disconnected edit? Is this a typical solution or are there easier/better ways of doing this? Any thoughts/suggestions would be greatly appreciated. Chris. |
#7
| |||
| |||
|
|
Hello Chris, Yep it can be as simple as that However have a look at this http://www.sqldts.com/default.aspx?204 Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Allan, thanks for the response...sorry to trouble you further but I have to ask what may be a dumb question. Is this as straightforward as exporting the row for my package from sysdtspackages on my "local" instance and then having someone at the "remote" instance import the data from the flat file directly into sysdtspackages on their instance? No gotchas? Will the remote DBA be able to open the package using DTS Designer after the import? Thanks again! Chris. "Allan Mitchell" wrote: Hello Chris, You can even have a flat file export of sysdtspackages as the medium. SSFs are though convenient as well. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com We are SS2K and need to move a package to other (remote) SS2K instances sitting behind firewalls. I read or heard somewhere, that transformations and mappings may be lost when opening a package in a different instance of SQL Server when the remote instance can't communicate with the instance on which the package was developed. Is there any value in saving the local package as a Structured Storage File and having the DBA at the remote site open the package from this file and then make the appropriate changes (like usernames and server I.P. address etc.) using disconnected edit? Is this a typical solution or are there easier/better ways of doing this? Any thoughts/suggestions would be greatly appreciated. Chris. |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.