November 18, 2010 at 4:22 pm
Hi Folks,
We recently changed the server name of one of our production 2008R2 MSSQL servers. After changing the applications connection strings and bouncing the server, the applications are working fine. The maintenance plans however are not.
It would appear that the SSIS package connection strings are still the old server name. I tried the simple create a new maintenance plan but the source from the SSIS stays the same. I imagine that the SSIS parameters are configured by the setup wizard during installation?
My question is that in a box stock standard installation, where / how does one change the parameters within / used by the SSIS packages?
This may be one of many tweaks needed after a server name change, hopefully the community here can make it less painfull for those of us about to undertake the change!
Thx
Paul.
November 18, 2010 at 5:10 pm
After some poking about, it appears that adding the new server name to the "manage connections" list was enough for MSSQL to work out that the local server connection name has changed and the new name now appears as the local server connection 🙂
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply