Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


rename SQL server


rename SQL server

Author
Message
sqlfriends
sqlfriends
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2047 Visits: 3863
george sibbald (3/7/2013)
Not sure I understand you:
You cannot be doing OS and SQL upgrades that often for this to be a problem?




you mentioned OS upgrades and new sql server versions in an earlier post, surely these are rare? If you mean just patches these are too quick to apply to warrant this approach.


We have some small applications developed in house.
And the window used to be windows 2003, and SQL is 2008.

We want to install windows 2008 R2 and SQL 2012.

For windows verison, it is not an upgrade, the box needs to be wiped out and resintall the new OS, and then intall new version of SQL, then migrating databases.
george sibbald
george sibbald
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6350 Visits: 13687
if resources are scarce its not for me to tell your company how to spend their money but a new server in prod to allow a side by side build would be really good, you'll want to refresh your hardware sooner or later. That will give you minimum downtime (and perhaps a cost saving?)

Putting the flexibility into the app code has got to be a worthwhile aim so perhaps use the test box as production for a while whilst you rebuild your production box, you'll have to isolate it as you cannot have two servers of the same name, and then migrate and repoint the app when its complete, hence the requirement for connection flexibility in the app.

As far as I can see the rename server would work if you go that way but as you can see its more than dropserver\addserver to be complete, its local groups and SSIS as well. I presume you are trying to minimise downtime so when do you rename the server, before or after the SQL install? Before would be better, no SQL issues then. As this is a total rebuild I presume you add SQL server level objects by script and atach the databases. That should be doable in a few hours.

Just some thoughts.

---------------------------------------------------------------------
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search