Post reply

Renaming a Virtual SQL Servername under SQL 2000 - without re-installing?

  • November 15, 2005 at 5:02 am

    #364167

    Is it possible to rename a Virtual SQL Servername (on SQL Server 2000) without re-installing SQL?

    If so, can anyone point me at instructions as to how this can be done?

    Thanks!

    Tom.

  • November 16, 2005 at 6:03 am

    #604168

    i wanted to do the same thing...you can't; you'll need to save all your data/backups,uninstall the old instance, and then install a new instance witht eh new "correct" name, and then restore the data on the new instance.

     

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • November 16, 2005 at 7:43 am

    #604204

    We did manage this but it is fraught with problems, the issue is getting each node to see the same name -- the issue is with the quorum registry info ( i'm told ! ).

    We swapped clusters in and out of production, whereby cluster fred became cluster jim ( where jim was our production cluster ) after testing jim was removed and became fred again. At some stage jim also became fred < grin ! >

    In fairness it did give us some problems, a failover on the cluster that was once in prodcution caused the production cluster to fail over. We did this with 3 clusters.

    The platforms guys are convinced they could do it again without problems but I'm not so sure.

    Best of luck ! We used 2000 , they say it would be easier with 2003.

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

  • November 16, 2005 at 12:08 pm

    #604262

    We had to reinstall a clustered SQL Server instance due to hardware upgrades and in the process changed the instance name to match with current standards. This left us with 700+ client computers looking for the old 'virtual instance' ... not one bit of a problem !!! A DNS alias fixed everything. So unless there is a compelling reason to change the virtual instance name, I'd say just leave it alone and use DNS instead.

    Oh, by the way, we have standardized (rebuilt/renamed) other clusters, both Win2K and Win2K3, successfully in the same fashion and not one client computer change was needed !

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • August 28, 2006 at 2:45 am

    #657030

    sp_dropserver

    go

    sp_addserver , local

    go

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply