SSIS Package Portability
-
I moved a SSIS Package from a computer A to a computer B.
I opened it on B. A number of tasks got the red bullet, obviously because the Connection Managers were no more valid. One could have expected that if the names of the servers, databases and tables were identical on A and B the Connection Managers would remain valid. Not so I’m afraid.
I tried to Edit one of the Sources in order to link it to the new Connection Manager. After more than one minute (on a powerful computer) during which VS was “Not Responding”, I got the following Massage Boxes:
=================================================
TITLE: Microsoft Visual Studio
------------------------------
Could not retrieve a connection manager for the selected connection object.
------------------------------
BUTTONS:
OK
=================================================
TITLE: Microsoft SQL Native Client
------------------------------
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
------------------------------
BUTTONS:
&Retry
Cancel
==================================================
After clicking Cancel I got in a loop:
- VS in Not Responding mode for a minute or so
- Click Cancel
- Back to 1
I guess the labels of the two buttons were swapped.
Obviously the conclusion is that, after moving to another computer, before trying to edit any component one should delete the existing Connection Managers.
The next not so nice portability problem is that even if one preserves the initial Connection Managers' names they are not recognised so you have to edit all components in order to link them to the new Connection Managers.
Is there another way?
Many thanks,
Dinu
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply