Database Journal
MS SQL Oracle DB2 Access MySQL PostgreSQL Sybase PHP SQL Etc SQL Scripts & Samples Links Database Forum

» Database Journal Home
» Database Articles
» Database Tutorials
MS SQL
Oracle
DB2
MS Access
MySQL
» RESOURCES
Database Tools
SQL Scripts & Samples
Links
» Database Forum
» Sitemap
Free Newsletters:
DatabaseDaily  
News Via RSS Feed


follow us on Twitter
Database Journal |DBA Support |SQLCourse |SQLCourse2
 

Featured Database Articles

MS SQL

Posted Apr 24, 2003

A Server by Any Other Name - Page 3

By DatabaseJournal.com Staff

by MAK [Muthusamy Anantha Kumar]

Process involved in SQL Server 7.0



Step 1: Ignore error messages

After changing the server and rebooting, you will get the following error messages.




Your SQL Server installation is either corrupt or has been tampered with (unknown package id). Please rerun Setup

Click 'OK'


At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.

Click 'OK'

Insert the SQL Server CD and run autorun.exe to run Setup.

Step 2 Run SQL Server setup

Click on "Install SQL Server 7.0 Components"

Depending on the SQL server edition that you installed select the edition.

Select "Local Install" and click next.

You will get the following message:

Click "Yes" to continue.

Click 'Finish'

Step 3 Update client network utility

Add the new server name.

Step 4 Register the new server name

Delete the old server registration and register the new server name.

Step 5 Update sysservers

use master
go
Use master
go
sp_configure 'allow updates',1
go
reconfigure with override
go
update sysservers set srvname = 'changeserver' where srvname ='oldservername'
go
sp_configure 'allow updates',0
go
reconfigure with override
go

Step 6 Update sysservers

Use master
go
sp_configure 'allow updates',1
go
reconfigure with override
go
use msdb
go
update sysjobs set originating_server ="oldservername" 
go
sp_configure 'allow updates',0
go
reconfigure with override
go

Note: Usually sysjobs will have the value '(local)' in sysjobs.originating_server column.

Step 7: update clients and other servers

Update all of the clients (Follow step3) to point to the new server and any linked server you have updated with the new name. Make sure any user DLLs and web servers pointing to the server name point to the new server name.




MS SQL Archives

Comment and Contribute

 


(Maximum characters: 1200). You have characters left.

 

 




Latest Forum Threads
MS SQL Forum
Topic By Replies Updated
SQL 2005: SSIS: Error using SQL Server credentials poverty 3 August 17th, 07:43 AM
Need help changing table contents nkawtg 1 August 17th, 03:02 AM
SQL Server Memory confifuration bhosalenarayan 2 August 14th, 05:33 AM
SQL Server Primary Key and a Unique Key katty.jonh 2 July 25th, 10:36 AM