Installation of SQL Server 2012 RTM on Windows Server 8 Beta (.NET 3.5 explained)

I made my first attempt to install SQL Server 2012 RTM on Windows Server 8 Beta on 07.03.2012 and as you may remember from that post, it failed on .NET Framework 3.5. I tried to install it again after having enabled .NET Framework 3.5 in Server Manager and this time it worked like charm. My conclusion is – check the prerequisites before and install all the missing ones in advance, don’t just rely on setup program to do it all for you. So this leaves me with two more tests to do:
1. Install SQL Server 2012 RTM on a fresh Windows Server 8 machine – to replicate the problem.
2. Install SQL Server 2012 RTM on a fresh Windows Server 2008 R2 machine – to see if it’s related to OS feature detection – if so -> Connect.

Now the general feeling of using SQL Server 2012 RTM is not much different from Denali CTP3 or 2012 RC0, I’m just having a very hard time getting used to Metro interface in Windows Server 8. For start – after installation of Master Data Services, SQL Server Data Tools, Data Quality Services and Database Engine I have two screens full of icons scattered all around instead of nice grouping. And – bad luck – SSMS is on the second screen 🙂

SQL Server 2012 feature selection on Windows Server 8 Beta

So, for the test #1: In Windows 8, when you select Database Engine at the Feature Selection dialog you have following information:

  • Power Shell 2.0 already installed – quite obvious
  • Visual Studio 2010 Shell and .NET Framework 4 to be installed – by SQL Server installer
  • .NET Framework 3.5 – Windows feature to be turned on

The installer does not check for .NET 3.5 availability in your system until actual installation, so you will complete whole setup wizard and get an error at the very end.

As far as test #2 is concerned – if you install SQL Server 2012 RTM on Windows Server 2008 R2 and you forget to enable .NET Framework 3.5, the installer will stop right after Feature Selection asking to fulfill the software requirements. Apart from .NET 3.5, any existing Visual Studio 2010 installation must be upgrade to SP1 to allow SQL Server 2012 to continue.

   

 

 

 

 

And if you go back to SQL Server 2008 R2, it will not even launch the setup landing page if you have .NET Framework 3.5 missing.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s