Skip to main content

Generic SQL Server 2008 R2 Installation

I recently had to create some virtual machine tempaltes which needed Microsoft SQL Server 2008 R2 installed on it, so I thought I'd document it as I went along.

In the example shown below, I'll be installing SQL Server on a machine running Windows Server 2008 R2 (Entreprise Edition). I'll be doing a very generic installation however if you need to customise it, it should not be too difficult.

Before You Begin

Before you begin, you will need the following:
  • Microsoft SQL Server 2008 R2 - ISO/DVD 
  • Visual Studio 2008 (With Service Pack 1 installed)

Installation Steps

  • On mounting the image you should get an autorun prompt which will bring up the setup application. If it does not show up, navigate to the base folder of the image and click on setup.exe
  • This should open up the SQL Server Installation Center as shown below
  • Click the Installation tab as shown below. This should open up the Setup Support Rules 
  • Now click the New installation or add features to an existing installation link as shown below
  •  Click OK and procees to the next step as shown below
  •  The installer should now prompt you for your Product Key. You can either enter a valid product key or choose the Evaluation edition as shown below. You then need to click Next.
  •  The install will then list the License Terms. Click the I accept the license checkbox as shown below and then click Next.
  • The installer will then try to install the Setup Support Files.  You need to click Install as shown below.
  • A new Setup Support Rules window will now pop up as shown below
  • Keep clicking Next till you reach the Setup Role window. Select the SQL Server Feature Installation radio button as shown below. (Note: If you want to add features to an existing installation, you need to select the last option and it will prompt you for an Instance Name. This option only shows up if you have an existing instance of SQL Server installed.)
  • Now choose the Select All check box and click Next. You then need to specify the Instance Name in the Instance Configuration section as shown below. (Note: By default the instance name is MSSQLSERVER but you can change this if you wish.)
  • The installer will then show you a Disk Usage Summary as shown below. Click Next & move on to the Server Configuration section.
  • In the Server Configuration section you need to click the Use the same account for all SQL Services button and choose NT AUTHORITY\NETWORK SERVICE. This account does not need a password to be entered.

  • In the Database Engine Configuration section select the Mixed Mode (Sql Server authentication and Windows authentication) option.
  • Enter a password for the SQL Server Administrator account (Note: The user name is sa) and also add your Windows account to the list of administrators by clicking the Add Current User button as shown below and click Next. You also need to add your Windows account in the Analysis Services Configuration section. (Note: You must remember the password that you typed in for the sa account!)

  • In the next section, select Install the native mode default configuration option to configure Reporting Services. Click Next. This should bring you to the Error Reporting section, click Next  again.

  • You should now see the Installation Configuration Rules screen. Click Next and proceed to the Ready to Install section as shown below. Now all you need to do is click Install.

  • This should start your installation. This will take a good 10 to 15 minutes depending on your machine so this would be a good time to get some coffee :) ...
  • The installer will prompt you when your installation has completed. You can now test you SQL Server by logging in using either your Windows credentials or your SQL Server credentials that you configured earlier. (Start - All Programs - Microsoft SQL Server 2008 R2 - SQL Server Management Studio)  

References: SQL Server Installation (SQL Server 2008 R2)


Post a comment

Popular posts from this blog

Internet Information Services(IIS) reveals its real or internal IP Address

In the ever changing world of global data communications, inexpensive Internet connections, and fast-paced software development, security is becoming more and more of an issue. Security is now a basic requirement because global computing is inherently insecure.

Keeping that in mind, we recently ran our flagship product through a security audit. It was such a helpful exercise in tying-off any remaining lose ends in our application in terms of application security. 
Based on the security audit report, there was a relatively minor issue that appeared when accessing the /images directory of our application. Turns out that the Location response header of the 301 request returns an Internal IP address. The issue is detailed below.

Issue reportedInternet Information Services (IIS) may reveal its real or internal IP address in the Location header via a request to the /images directory. The value returned whilst pen testing is

The riskInformation regarding internal IP add…

Unit Testing HttpContext.Current.Session in MVC3 .NET

We recently changed some functionality where during the "CREATE" process, we go through a wizard to save application data. This data is saved only to the session in the final step when the user clicks the final submit.

This was easy enough to implement but when I started writing unit tests for my static methods that Add, Update, Delete or Modify the contents of our application data in the session, I got the following error:
System.NullReferenceException: Object reference not set to an instance of an object.

Turns out I had forgotten to setup the HttpContext.
The following "TestInitialise" method fixed my problem :)

public void TestSetup()
// We need to setup the Current HTTP Context as follows:

// Step 1: Setup the HTTP Request
var httpRequest = new HttpRequest("", "http://localhost/", "");

// Step 2: Setup the HTTP Response
var httpResponce = new HttpResponse(new StringWriter());

// Step 3: Se…

IIS Request Filtering to block HTTP Verbs (For example Trace)

The issueRequest Filtering is a built-in security feature that was introduced in Internet Information Services (IIS) 7.0. This can be used to block specific verbs like "Trace".

When request filtering blocks an HTTP request, IIS 7 will return an HTTP 404 error to the client and log the HTTP status with a unique substatus that identifies the reason that the request was denied. Verb Denied.

HTTP SubstatusDescription404.5URL Sequence Denied404.6Verb Denied404.7File Extension Denied404.8Hidden Namespace404.1Request Header Too Long404.11URL Double Escaped404.12URL Has High Bit Chars404.13Content Length Too Large