The only thing that might get you is SPN (Service Principal Names) that might be registered in AD with the old name and new name that might need cleaned up. Otherwise, a side by side migration is always the safest.
Z Edward E. Ziots, CISSP, CISA, Security +, Network + Security Engineer Lifespan Organization [email protected] Work:401-255-2497 This electronic message and any attachments may be privileged and confidential and protected from disclosure. If you are reading this message, but are not the intended recipient, nor an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you are strictly prohibited from copying, printing, forwarding or otherwise disseminating this communication. If you have received this communication in error, please immediately notify the sender by replying to the message. Then, delete the message from your computer. Thank you. [Description: Description: Lifespan] From: [email protected] [mailto:[email protected]] On Behalf Of Jesse Rink Sent: Monday, August 12, 2013 3:52 PM To: [email protected] Subject: [NTSysADM] RE: sql server upgrade thanks damien and glen. i think i'll go ahead with option #2. i already have the MS tech article on how to rename a sql server so that isn't a concern. appreciate the insight. jesse ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]] on behalf of Glen Johnson [[email protected]] Sent: Monday, August 12, 2013 2:43 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: sql server upgrade +100 on option 2. I personally wouldn't trust option one, way too many strange things happen later and you never know if they are related to the upgrade or not. Plus, I never do OS upgrades. Never, never, never. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jesse Rink Sent: Monday, August 12, 2013 3:34 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] sql server upgrade We have an older Windows 2003 R2 x64 VM server which contains SQL2005 x64 on it. I'm planning on getting this box more current... My first option is to: 1. Take a image backup of the VM with our PHD Virtual software 2. Increase the c: drive hard disk in vSphere and then use a partition tool to expand the c: partition (its too small to perform the 2008 R2 upgrade on it) 3. Upgrade 2003 R2 x64 to Windows 2008 R2. 4. Upgrade SQL 2005 to SQL 2008 R2. Anyone had bad experiences going this route? The second option is to: 1. Create a brand new 2008 R2 server with SQL 2008 R2. 2. Detach the 10 DBs from SQL-OLD, copy them over to the SQL-NEW server and re-attach. 3. Decomission the old SQL-OLD server 4. Rename SQL-NEW to SQL-OLD and assign it the same IP address that the original SQL-OLD had. 5. Setup my Maintenance Plans from scratch. I think I'll be good for all my client applications that have specific ODBC settings configured pointing to either the IP address of the SQL box or the computer name/FQDN. Anyone had bad experiences going this route? Leaning more towards option TWO at this time... I tend to like clean installs as opposed to upgrades (generally). JR
<<inline: image001.jpg>>
