|
|
|
|
||||||
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
I have an issue where SQL 2005 server was renamed from Windows (i.e. the
server name was changed in Windows), Then I renamed the SQL server instance to be as the same as the new Windows name (using SP_DropServer, SP_Addserver ); now, all the maintenance plan jobs are not working. After looking further, I found that the "Local Server Connection" (in the maintenance plan), is still pointing to the OLD server name, and it is grayed out, (I could not change it). I know the solution is to create a new "Local Server Connection", and create a new maintenance plan, but this is not what I need. Is there anyway, I can modify the "Local Server Connection" to point to the new server name, like where it is stored in MSDB, in a file, or registry? Appreciate any . |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
"wit1" <wit1@hotmail.com> wrote in message news:uKfAqE2zIHA.1772@TK2MSFTNGP03.phx.gbl... >I have an issue where SQL 2005 server was renamed from Windows (i.e. the > server name was changed in Windows), > > Then I renamed the SQL server instance to be as the same as the new > Windows > name (using SP_DropServer, SP_Addserver ); now, all the maintenance plan > jobs are not working. > > > > After looking further, I found that the "Local Server Connection" (in the > maintenance plan), is still pointing to the OLD server name, and it is > grayed out, (I could not change it). > > I know the solution is to create a new "Local Server Connection", and > create > a new maintenance plan, but this is not what I need. > > > > Is there anyway, I can modify the "Local Server Connection" to point to > the > new server name, like where it is stored in MSDB, in a file, or registry? > > > > Appreciate any . > > Hi Can you create a "New Local Server Connection" and change the connection for each task? John |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Yes, I can, but this is not what I need.
I need to know how I can change the "Local Server Connection" to reflect the new instance name. Thanks. "John Bell" <jbellnewsposts@hotmail.com> wrote in message news:C410B17D-38A5-42BC-9425-2469B330E1A8@microsoft.com... > > "wit1" <wit1@hotmail.com> wrote in message > news:uKfAqE2zIHA.1772@TK2MSFTNGP03.phx.gbl... > >I have an issue where SQL 2005 server was renamed from Windows (i.e. the > > server name was changed in Windows), > > > > Then I renamed the SQL server instance to be as the same as the new > > Windows > > name (using SP_DropServer, SP_Addserver ); now, all the maintenance plan > > jobs are not working. > > > > > > > > After looking further, I found that the "Local Server Connection" (in the > > maintenance plan), is still pointing to the OLD server name, and it is > > grayed out, (I could not change it). > > > > I know the solution is to create a new "Local Server Connection", and > > create > > a new maintenance plan, but this is not what I need. > > > > > > > > Is there anyway, I can modify the "Local Server Connection" to point to > > the > > new server name, like where it is stored in MSDB, in a file, or registry? > > > > > > > > Appreciate any . > > > > > Hi > > Can you create a "New Local Server Connection" and change the connection for > each task? > > John > |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
"wit1" <wit1@hotmail.com> wrote in message news:eoyGLe7zIHA.4476@TK2MSFTNGP06.phx.gbl... > Yes, I can, but this is not what I need. > I need to know how I can change the "Local Server Connection" to reflect > the > new instance name. > > Thanks. > > "John Bell" <jbellnewsposts@hotmail.com> wrote in message > news:C410B17D-38A5-42BC-9425-2469B330E1A8@microsoft.com... >> >> "wit1" <wit1@hotmail.com> wrote in message >> news:uKfAqE2zIHA.1772@TK2MSFTNGP03.phx.gbl... >> >I have an issue where SQL 2005 server was renamed from Windows (i.e. the >> > server name was changed in Windows), >> > >> > Then I renamed the SQL server instance to be as the same as the new >> > Windows >> > name (using SP_DropServer, SP_Addserver ); now, all the maintenance >> > plan >> > jobs are not working. >> > >> > >> > >> > After looking further, I found that the "Local Server Connection" (in > the >> > maintenance plan), is still pointing to the OLD server name, and it is >> > grayed out, (I could not change it). >> > >> > I know the solution is to create a new "Local Server Connection", and >> > create >> > a new maintenance plan, but this is not what I need. >> > >> > >> > >> > Is there anyway, I can modify the "Local Server Connection" to point to >> > the >> > new server name, like where it is stored in MSDB, in a file, or > registry? >> > >> > >> > >> > Appreciate any . >> > >> > >> Hi >> >> Can you create a "New Local Server Connection" and change the connection > for >> each task? >> >> John >> But it may be the quickest solution. John |
|
![]() |
| Outils de la discussion | |
|
|