Uninstalling SQL 2012 - What should I tick or leave un-ticked?

[TwistedHelixis]

Hi all,

 

At some point the LA migrated SIMS etc from SQL 2012 to SQL 2016. I have just noticed that SQL 2012 was never uninstalled.

 

On a test server, I am running through the SQL 2012 uninstall process, but not sure which of the following check boxes I should tick or leave un- ticked?

 

 

Hoping someone more knowledgeable can help :-)

[Squelch]

I have remains of several versions of SQL listed on my SIMS server, I just leave them there in case removing them causes unforeseen problems.

[mrbios]

Assuming no databases are running on the 2012 instance you can safety remove Database engine services and SQL server replication and just leave the rest which won't take up much space anyway.

[KK20]

Do you mean an inplace upgrade of 2012 to 2016? There tends to be stubs left behind but ive never seen an inplace upgrade that has left significant binaries behind. If it is a parallel install and migration then I would say all of the 2012 can be removed (assuming you didnt use any other DB on there - WSUS etc). I think 2016 still has integrated reporting services so that should have moved with the installation if it is a parallel install. I cannot remember what happens to reporting services with an inplace upgrade (I moved to standalone reporting services)

[TwistedHelixis]

Do you mean an inplace upgrade of 2012 to 2016?

No, they installed SQL 2016 alongside 2012.

[TwistedHelixis]

I have had 3 answers and 3 different options :-)

 

leave it

remove just the Database engine services and SQL server

remove everything

 

Unless anyone chimes in, think I will go with the middle option.

 

Thanks

[TwistedHelixis]

So on a test VM, I uninstalled just the Database engine services and SQL server, but when I opened SQL database manger it still listed the 2012 instance. Clicking on this then gave an error message.

 

Is this normal?

 

I am going to try uninstalling everything on my test vm next.

[TwistedHelixis]

Hmmmm

 

Just fully uninstalled SQL 2012 (ticked all options to be removed) and it still gets listed as an instance in SQL manager.

 

Any ideas?

[TwistedHelixis]

Sorry, just realised that using the word 'instance' in my last 2 posts might have been confusing......

 

After running through both uninstall options, the SQL 2012 database is still listed in the drop down menu in SQL management studio. After doing the FULL uninstall SQL 2012 is not listed anymore in 'Add remove programs', so not sure why its still listed in management studio.

[KK20]

does it still list if you attempt to connect to a database engine, go to "server name" dropdown -> browse for more -> network servers and expand database engine? That is odd if it does as that means there is a pipe being broadcast. You could always install and run "microsoft assessment and planning tool" and run a search on your network for SQL servers, that will tell you definitively what is running (and is a good idea to pick up on those old SQL express installs from old programs such as Sophos etc that left those databases behind)

[TwistedHelixis]

does it still list if you attempt to connect to a database engine, go to "server name" dropdown -> browse for more -> network servers and expand database engine?

No, it just lists the newer SQL2016

 

You could always install and run "microsoft assessment and planning tool" and run a search on your network for SQL servers,

I am testing this on a host VM that is not connected to our network, The server should only have access to the test VM DC and itself. Should I still run the "microsoft assessment and planning tool"?

[TwistedHelixis]

I have just noticed that after doing a FULL uninstall I do still have 'MS SQL server 2012 native client' left in 'add remove programs' should I uninstall this?

[TwistedHelixis]

Just found the answer. Management studio apparently uses a cache of recently connected databases. I can just ignore the issue or re install SQL management studio.