Changing the SQL Server Name

I have SQL 2000 std installed on a win2000 box with latest svc packs and box
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thks
Did SQL Server start with an error along the lines of "has beeen tampered
with?"
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
In order to fix the jobs you will have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
Keith
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>
|||Some info here: http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and box
> was originally designated with a development name which SQL also inherited.
> Now the server box name has been changed but the server still indicates the
> old box name.
> What are the implications if I leave as is and how difficult is it to change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan and
> had to be re-defined.
> thks
>

Changing the SQL Server Name

I have SQL 2000 std installed on a win2000 box with latest svc packs and box
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thksDid SQL Server start with an error along the lines of "has beeen tampered
with?"
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
In order to fix the jobs you will have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
Keith
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>|||Some info here: http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and bo
x
> was originally designated with a development name which SQL also inherited
.
> Now the server box name has been changed but the server still indicates th
e
> old box name.
> What are the implications if I leave as is and how difficult is it to chan
ge
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan an
d
> had to be re-defined.
> thks
>

Changing the SQL Server Name

I have SQL 2000 std installed on a win2000 box with latest svc packs and box
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thksDid SQL Server start with an error along the lines of "has beeen tampered
with?"
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
In order to fix the jobs you will have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
Keith
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>|||Some info here: http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and box
> was originally designated with a development name which SQL also inherited.
> Now the server box name has been changed but the server still indicates the
> old box name.
> What are the implications if I leave as is and how difficult is it to change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan and
> had to be re-defined.
> thks
>

Changing IP Number on SQL 2000 Std

I am changing the IP Number on a Win 2003 Enterprise Server running SQL 2000
Std. This SQL servert is accessed by a second machine running a SharePoint
web site.
After changing the numbers to the new network on both machines and rebooting
both machines, I get "SQL Server does not exist or access denied".
I can ping each machine from the other getting the new ip numbers, I can see
the machines from each other via NetBios.
Is there something else that needs to be done?
Paul@.CommerceStreet.comDoes sqlserver listen on the new ip. Take a quick look at sqlserver ERRORLOG
for this info.
You also want to run cliconfg.exe to see if you have your Sharepoint
pointing to the correct server/IP.
"Paul@.CommerceStreet.com"
<Paul@.CommerceStreet.com@.discussions.microsoft.com> wrote in message
news:16E6AD58-39D6-4798-A194-6BBF8790A227@.microsoft.com...
> I am changing the IP Number on a Win 2003 Enterprise Server running SQL
2000
> Std. This SQL servert is accessed by a second machine running a SharePoint
> web site.
> After changing the numbers to the new network on both machines and
rebooting
> both machines, I get "SQL Server does not exist or access denied".
> I can ping each machine from the other getting the new ip numbers, I can
see
> the machines from each other via NetBios.
> Is there something else that needs to be done?
> Paul@.CommerceStreet.com|||running cliconfg.exe and changing the IP Number seems to have fixed the
problem. Thanks!
PF
"oj" wrote:
> Does sqlserver listen on the new ip. Take a quick look at sqlserver ERRORLOG
> for this info.
> You also want to run cliconfg.exe to see if you have your Sharepoint
> pointing to the correct server/IP.
>
> "Paul@.CommerceStreet.com"
> <Paul@.CommerceStreet.com@.discussions.microsoft.com> wrote in message
> news:16E6AD58-39D6-4798-A194-6BBF8790A227@.microsoft.com...
> > I am changing the IP Number on a Win 2003 Enterprise Server running SQL
> 2000
> > Std. This SQL servert is accessed by a second machine running a SharePoint
> > web site.
> >
> > After changing the numbers to the new network on both machines and
> rebooting
> > both machines, I get "SQL Server does not exist or access denied".
> >
> > I can ping each machine from the other getting the new ip numbers, I can
> see
> > the machines from each other via NetBios.
> >
> > Is there something else that needs to be done?
> >
> > Paul@.CommerceStreet.com
>
>

Changing IP Number on SQL 2000 Std

I am changing the IP Number on a Win 2003 Enterprise Server running SQL 2000
Std. This SQL servert is accessed by a second machine running a SharePoint
web site.
After changing the numbers to the new network on both machines and rebooting
both machines, I get "SQL Server does not exist or access denied".
I can ping each machine from the other getting the new ip numbers, I can see
the machines from each other via NetBios.
Is there something else that needs to be done?
Paul@.CommerceStreet.com
Does sqlserver listen on the new ip. Take a quick look at sqlserver ERRORLOG
for this info.
You also want to run cliconfg.exe to see if you have your Sharepoint
pointing to the correct server/IP.
"Paul@.CommerceStreet.com"
<Paul@.CommerceStreet.com@.discussions.microsoft.com > wrote in message
news:16E6AD58-39D6-4798-A194-6BBF8790A227@.microsoft.com...
> I am changing the IP Number on a Win 2003 Enterprise Server running SQL
2000
> Std. This SQL servert is accessed by a second machine running a SharePoint
> web site.
> After changing the numbers to the new network on both machines and
rebooting
> both machines, I get "SQL Server does not exist or access denied".
> I can ping each machine from the other getting the new ip numbers, I can
see
> the machines from each other via NetBios.
> Is there something else that needs to be done?
> Paul@.CommerceStreet.com
|||running cliconfg.exe and changing the IP Number seems to have fixed the
problem. Thanks!
PF
"oj" wrote:

> Does sqlserver listen on the new ip. Take a quick look at sqlserver ERRORLOG
> for this info.
> You also want to run cliconfg.exe to see if you have your Sharepoint
> pointing to the correct server/IP.
>
> "Paul@.CommerceStreet.com"
> <Paul@.CommerceStreet.com@.discussions.microsoft.com > wrote in message
> news:16E6AD58-39D6-4798-A194-6BBF8790A227@.microsoft.com...
> 2000
> rebooting
> see
>
>

Changing IP Number on SQL 2000 Std

I am changing the IP Number on a Win 2003 Enterprise Server running SQL 2000
Std. This SQL servert is accessed by a second machine running a SharePoint
web site.
After changing the numbers to the new network on both machines and rebooting
both machines, I get "SQL Server does not exist or access denied".
I can ping each machine from the other getting the new ip numbers, I can see
the machines from each other via NetBios.
Is there something else that needs to be done?
Paul@.CommerceStreet.comDoes sqlserver listen on the new ip. Take a quick look at sqlserver ERRORLOG
for this info.
You also want to run cliconfg.exe to see if you have your Sharepoint
pointing to the correct server/IP.
"Paul@.CommerceStreet.com"
<Paul@.CommerceStreet.com@.discussions.microsoft.com> wrote in message
news:16E6AD58-39D6-4798-A194-6BBF8790A227@.microsoft.com...
> I am changing the IP Number on a Win 2003 Enterprise Server running SQL
2000
> Std. This SQL servert is accessed by a second machine running a SharePoint
> web site.
> After changing the numbers to the new network on both machines and
rebooting
> both machines, I get "SQL Server does not exist or access denied".
> I can ping each machine from the other getting the new ip numbers, I can
see
> the machines from each other via NetBios.
> Is there something else that needs to be done?
> Paul@.CommerceStreet.com|||running cliconfg.exe and changing the IP Number seems to have fixed the
problem. Thanks!
PF
"oj" wrote:

> Does sqlserver listen on the new ip. Take a quick look at sqlserver ERRORL
OG
> for this info.
> You also want to run cliconfg.exe to see if you have your Sharepoint
> pointing to the correct server/IP.
>
> "Paul@.CommerceStreet.com"
> <Paul@.CommerceStreet.com@.discussions.microsoft.com> wrote in message
> news:16E6AD58-39D6-4798-A194-6BBF8790A227@.microsoft.com...
> 2000
> rebooting
> see
>
>