Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / July 2008

Tip: Looking for answers? Try searching our database.

Will this work?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ron - 30 Jun 2008 22:26 GMT
We currently have a production server that needs replacing.  Current server
is prod01 with default instance of sql2000.  We are building a replacement
server prod02 with default instance of sql2005.  Once the replacement server
is built and all databases are copied, the plan is to shutdown prod01 and
take it out of the domain, then rename prod02 to prod01 as well as giving the
replacement server the same ip address.

Will this rename the default instance as well?  Will all app servers that
connected to prod01 now be able to connect to the new prod01 seemlessly?

The reason this approach is being suggested is due to the fact that the app
servers can not be changed (for various reasons) to point to another server.

Thanks

Ron
Rick Sawtell - 30 Jun 2008 23:21 GMT
> We currently have a production server that needs replacing.  Current
> server
[quoted text clipped - 17 lines]
>
> Ron

This can be done, however, you should also reset the SQL Server internals.
I believe the command is:

sp_dropserver <old default server name Prod02>
sp_addserver <new default server name Prod01>

I have not done this in quite a while however.  Maybe someone else has some
additional gotcha's to look out for.

Rick Sawtell
Tibor Karaszi - 01 Jul 2008 00:10 GMT
Yep, just make sure you add below when adding back the server with the proper name:

, LOCAL

Signature

Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi

>> We currently have a production server that needs replacing.  Current server
>> is prod01 with default instance of sql2000.  We are building a replacement
[quoted text clipped - 23 lines]
>
> Rick Sawtell
bass_player - 01 Jul 2008 06:53 GMT
Another approach is to do it on the DNS, assuming you are using DNS to
access your SQL Servers. No need to replace the servername but the instance
name should be the same.  Once you managed to change IP addresses, it's as
if nothing happened

>> We currently have a production server that needs replacing.  Current
>> server
[quoted text clipped - 29 lines]
>
> Rick Sawtell
Ron - 01 Jul 2008 16:04 GMT
Thanks Guys.

> We currently have a production server that needs replacing.  Current server
> is prod01 with default instance of sql2000.  We are building a replacement
[quoted text clipped - 12 lines]
>
> Ron
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.