I have an Integration Services package that processes an Analysis Services database. The Connection Manager for the database is set up at the project level (Project Deployment Model). The package works fine from my computer.
When I deploy the package along with the rest of the project to the server it will no longer process the database.
I configured the ServerName property of the connection manager to the appropriate server for that environment but the Connection Manager still tries to connect to the server specified in the
ConnectionString property. It's like the ServerName
property is completely ignored or the value of the ConnectionString
property is being applied after the other properties.
If I configure the ConnectionString property to connect to the proper server the package will run as expected; however, configuring each connection string will not work for us. We have several dozen AS databases and when (not if) the server name changes we'll have to change the connection string for each database.
Other things I tried but didn't work:
- Configured the ConnectionString property to be blank hoping the connection manager would build it from the supplied properties.
- Left the Data Source parameter in the ConnectionString property blank hoping the connection manager would pull it from the ServerName property.