April 30, 2015 at 12:22 pm
WHEE! I just got my new servers and am ready to install SQL 2012 when I discovered that one of these servers already has it installed (and incorrectly).
So before I go to do the usual uninstall, I wanted to ask. Are there any caveats or special post-uninstall cleanups that I will need to be aware of / do before reinstalling SQL on that server?
It's a Windows 2012 OS (I think Enterprise), if that makes a difference. 64 bit.
April 30, 2015 at 12:54 pm
Quick thought, safe your self from any future grieve and wipe it! In other words, do a fresh install of the OS and the SQL Server.
😎
May 1, 2015 at 2:29 am
Yep: safest bet is to nuke the entire server from orbit. It's the only way to be sure.
I've had too many problems in the past with nasties clinging on from previous installations...
May 1, 2015 at 5:18 am
The problem is that I can't nuke the OS. Corporate has to build servers (we're not allowed) and we had to pull teeth in order to get our new servers. If we try to get the server redone, it'll be a year before we'll get it back (other departments have priority after this build) and Bad Things will happen with our current environment.
In the absence of nuking the server, any advice?
May 1, 2015 at 5:22 am
Brandie Tarvin (5/1/2015)
The problem is that I can't nuke the OS. Corporate has to build servers (we're not allowed) and we had to pull teeth in order to get our new servers. If we try to get the server redone, it'll be a year before we'll get it back (other departments have priority after this build) and Bad Things will happen with our current environment.In the absence of nuking the server, any advice?
You could use System Restore to the earliest point available, patch the OS and then install the SQL Server.
😎
May 1, 2015 at 5:25 am
Eirikur Eiriksson (5/1/2015)You could use System Restore to the earliest point available, patch the OS and then install the SQL Server.
😎
That's a pretty good idea!
Otherwise, it'll be just the usual then:-
Back up any databases from the old instance that you think might become useful
Script any old jobs and other server objects that you may need
Save any packages and what-have-you
Then use the regular uninstall method to get rid of it. Check the registry afterwards for anything that might bite you - I have no specific recommendations for this, but I seem to remember finding the odd thing over the years.
Good luck!
May 1, 2015 at 5:29 am
EMarkM (5/1/2015)
Eirikur Eiriksson (5/1/2015)You could use System Restore to the earliest point available, patch the OS and then install the SQL Server.
😎
That's a pretty good idea!
Otherwise, it'll be just the usual then:-
Back up any databases from the old instance that you think might become useful
Script any old jobs and other server objects that you may need
Save any packages and what-have-you
Then use the regular uninstall method to get rid of it. Check the registry afterwards for anything that might bite you - I have no specific recommendations for this, but I seem to remember finding the odd thing over the years.
Good luck!
HA! Fortunately it is literally a brand new install of SQL. Nothing has been done to it. We just got the server yesterday and I was checking the configurations when I noticed it had issues. So nothing to back up. I can nuke the SQL install without worrying about losing anything. @=)
I'll check the System Restore stuff and see if there's a point where I can revert to pre-SQL install. Thanks, all.
May 1, 2015 at 6:32 am
Brandie Tarvin (4/30/2015)
WHEE! I just got my new servers and am ready to install SQL 2012 when I discovered that one of these servers already has it installed (and incorrectly).So before I go to do the usual uninstall, I wanted to ask. Are there any caveats or special post-uninstall cleanups that I will need to be aware of / do before reinstalling SQL on that server?
It's a Windows 2012 OS (I think Enterprise), if that makes a difference. 64 bit.
The uninstall is very effective, you should not have any issues at all
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 1, 2015 at 7:20 am
Perry Whittle (5/1/2015)
Brandie Tarvin (4/30/2015)
WHEE! I just got my new servers and am ready to install SQL 2012 when I discovered that one of these servers already has it installed (and incorrectly).So before I go to do the usual uninstall, I wanted to ask. Are there any caveats or special post-uninstall cleanups that I will need to be aware of / do before reinstalling SQL on that server?
It's a Windows 2012 OS (I think Enterprise), if that makes a difference. 64 bit.
The uninstall is very effective, you should not have any issues at all
That is good to hear. Thanks, Perry.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply