With the release of Windows Server 2012 I thought I would take the opportunity to look at running SQL 2012 Core on Windows Server 2012.
This blog is part 2 of a series which will look at the configuration for installing SQL 2012 Core on Windows Server Core, and then finish with adding AlwaysOn functionality to the environment.
In Part 1 of this series we covered building the Management Server (SQL2012-MGMT) and the SQL Server (SQL2012-01)
IMPORTANT: It is important to highlight that there are particular requirements for installing SQL Server on Windows 2012 and those are available at http://support.microsoft.com/kb/2681562/EN-US. For SQL 2012 the RTM release is supported on Windows 2012 however you should always refer to the official MSDN documentation to verify your hardware and software requirements (for SQL 2012 see http://msdn.microsoft.com/en-us/library/ms143506.aspx). It is also important to note that this work is out of pure interest within an isolated LAB environment and does not represent any official supportability of this configuration, it is based on my experience when configuring the environment and you should verify the suitability and supportability of such configuration within your own environment.
Step 1 - SQL Install (SQL2012-01)
In this step we need to complete the SQL install on the Windows Server 2012 Core installation. As there is no GUI the install needs to be performed using an unattended install file and from the command line.
Step 2 - Post SQL Install Configuration (SQL2012-01)
In this step we need to configure the additional settings like memory, TCP ports, etc, but more importantly this shows how to remotely manage your SQL Install.
Step 3 - Testing and Provisioning
Now that your SQL Installation is complete and you have performed your initial configuration steps, the next steps are.
Of cause this is best practise, in my Lab environment I am going to assume I know what I am doing (famous last words!)
Congratulations your SQL Server 2012 Core install on Windows Server 2012 Core is now complete.
In the follow up blog to this series we will start to configure the AlwaysOn high availability feature.