We installed RC0 the day it was released and, for needs of space and project transitioning, needed to reclaim the space.

As I couldn't find an uninstall option in the installation UI, I resorted to the right-click and uninstall via the Programs and Features control panel list. Up comes the 3 options and Remove is what I needed.

The uninstall stated all green ticks for all components, having selected everything available.

Once closed out, the P&F list still shows everything present, albeit the version and size against the 64-bit SQL Server program are cleared out.

I can still right-click and remove, which is weird, so, seeing only the SDK, check that, remove and it clears a few more things that weren't in the selection list. More weird.

Reboot the server! Done. Entrails are still all there. Huh? Right-click remove, same SDK there, select, remove, more unlisted things removed.

Resorted to individually removing the 2016 artifacts, many and various, not all starting with a common name, of course, so look for "2016" and whack away. Lots of "if you whack this, x and y and 20 others won't work..." warnings. Whacked 'em.

So, I'm still left with:

  1. Microsoft SQL Server 2016 RC0 (64-bit) - no size or version
  2. Microsoft SQL Server 2016 RC0 Setup (English)

Stubborn little diggers.

Does anyone have any advice on how to cleanse the server of RC0, please, especially as we'll likely put RTM on the machine when the time comes..

Thanks in advance (from an accidental DBA)

  • Is a clean Windows install an option? I'm not sure if it's your only 100% safe option but I'd consider not installing any RC version in a system that is used for other things. You can always test beta and RC versions in a VM (that can be easily dropped afterwards). – ypercubeᵀᴹ Apr 1 '16 at 12:42
  • @ypercube: Fresh Windows isn't any kind of option. As we had no issues at all with installing and removing CTPs starting at 2.2 up through the 3.x iterations, we, foolishly, were as confident about RC0 as CTP#. – SAinCA Apr 4 '16 at 20:40
  • Not that it'll help you now but I've grown a habit of installing prerelease software inside a VM. That way, If I break stuff I just restore a VM snapshot or spin up a new VM from an image somewhere. – Tom V Apr 4 '16 at 20:46
  • I've only installed 2016 on throwaway machines; usually running Windows 2016 TP 4; the only "upgrade" path is a new VM. – Anti-weakpasswords Apr 13 '16 at 22:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.