How to Install SQL Server 2008

A Step by Step guide to installing SQL Server 2008 simply and successfully with no prior knowledge

Developers and system administrators will find this installation guide useful, as will seasoned DBAs. It will teach you the basics required for a typical, problem-free installation of SQL Server 2008, allowing you to add other components later if you wish.

Remember to install the .Net Framework 3.5

Before you start the installation, you’ll need to install the .Net 3.5 Framework. This comes pre-installed on Windows 2008 Server, but for earlier versions of Windows, you’ll need to install it first. This is a straightforward pre-requisite and is usually included as part of the SQL Server 2008 installation. However, if you don’t know how to do this, or for some reason you need to download it, check out the guide Installing .Net Framework 3.5 for SQL Server 2008.

Once this Framework in installed you can commence the installation of SQL Server 2008.

STEP 1 : Copy the installation files

First off I’d recommend you copy the entire directory structure from the SQL Server 2008 installation disc to the C: drive of the machine you are going to install it on.

Although this means you need to grab a cup of coffee whilst it’s copying, this has three advantages:

  • It makes the installation process much faster than running it from CD/DVD once it gets started.
  • It allows you to easily add or remove components later, without having to hunt around for the CD/DVD.
  • If your media is damaged and a file won’t copy, you get to find out now, rather than halfway through the installation.

Here’s what my system looks like after the copy:

STEP 2 : Setup.exe

Double click on the setup.exe file.
After a few seconds a dialog box appears:

This will disappear from the screen and then the main installation page appears:

STEP 3 : SQL Server Installation Center

Click on the Installation hyperlink on the left hand side of the screen:

STEP 4 : SQL Server Installation Center

Click on the “New Server stand-alone installation” link on the right side of the screen:

The following dialog appears on the screen whilst the install program prepares for installation:

After a minute or so (the timing will vary according to your system), the following screen appears:

STEP 5 (optional) :

If any checks have failed, click on the Show details button or “View detailed report link” to find out the cause, correct it, then click on the Re-run button to perform the checks again.

STEP 6 : Product key

If all checks have passed, click on the OK button. After a few moments, the option to select the edition and to enter the license key (or “product key”) will appear. Note that the product key box may already be populated, depending on which edition you have. Don’t enter the product key we’ve shown here, it won’t work on your system!:

STEP 7 : License Terms

Enter the product key into the box, or choose the free edition if you’re evaluating SQL Server 2008, and click on the Next button:

Click in the “I accept the license terms” check box, then click on the Next button again.

STEP 8 : Setup Support Files

The following screen appears; click on the Install button:

The following screen will appear whilst Windows Installer prepares itself for the installation. This will take a short while:

After 30 seconds or so the dialog appears again:

STEP 9 : Setup Support Rules

If all is well, the following screen appears:

Click on the Next button again.

STEP 10 : Feature Selection

Select the features you want to install.
At a minimum, the following are useful (I’d argue essential), but what you need will depend on your needs:

Click on the Next button.

STEP 11 : Instance Configuration

After a short while the following screen appears:

For most installations, keep the default settings.
Click on the Next button.

STEP 12 : Disk Space Requirements

This screen just tells you if you have sufficient disk space on the drive you’re installing to, and what’s going to be installed where.

Click on Next.

STEP 13 : Server Configuration

This step allows you to set up the service accounts that will be used to run SQL Server. If you have created Windows NT or Active Directory accounts for use with services, use these.

If not, then just to get the installation up and working, use the built-in Network Service account for all three services listed (this account does not require a password).

This allows SQL Server to start up after installation. However, it can be easily changed later to another account through the Services applet (Control Panel -> Administrator Tools -> Services):

In addition, remember to change the Startup Type to Automatic, for all three services. This automatically starts the SQL Server database engine, SQL Agent and SQL Browser services when the server is re-booted.

The first service runs the SQL Server database engines executable process. The other two services allow scheduled jobs to run after installation (and after a re-boot), and allow the SQL Server to be found by clients on the network.

Do not worry about changing the collation tab, unless there is a specific requirement for anything other than the default collation sequence. Finally, click on Next.

STEP 14 : Database Engine Configuration – Account Provision

This screen allows you to set up database engine security.

Change the Authentication Mode to Mixed Mode unless you are certain you only need Windows-only authentication.

  • Many third party applications rely on SQL Server logins to operate correctly, so if you are setting up a server for a third party application, rather than one developed in-house, enabling Mixed Mode authentication is a good idea.

If you pick Mixed Mode security, you must also enter a password for the sysadmin account (sa).

Enter and confirm a secure password for the sa account and keep it somewhere safe. Do not give it to any one you do not want to have access to the SQL Server.

Note that you MUST also provide a Windows NT account on the local machine as a SQL Server administrator. If you do not want Windows system administrators to be able walk up to the box and login to SQL Server, create a new, local, dummy Windows user and add this account instead. Otherwise, add in the local administrator account, or your own Windows account on the domain in which the SQL Server will reside.

STEP 15 : Database Engine Configuration – Data Directories

Click on the Data Directories tab.

Change the directories to specify which drives in your system will be used for the various types of database files.

Generally it’s advisable to put the User database directory and User log directory on separate physical drives for performance, but it will depend on how Windows has been configured and how many disk drives you have available.

If you are installing on a single drive laptop or desktop, then simply specify:

Data root directory C:\Program Files\Microsoft SQL Server
User database directory C:\Data
User log directory C:\Logs
Temp DB directory C:\TempDB
Temp Log directory C:\TempDB
Backup directory C:\Backups

Do not click on the FILESTREAM tab unless you know you need to change these options, as it is not generally required for most installations, but can easily be changed by using sp_configure ‘filestream_access_level’, ”after SQL Server has been installed. Click on Next.

STEP 16 : Error Usage Reporting

This screen simply asks if you want to send error information to Microsoft and can safely be skipped if you do not want to share any information.

Click boxes if you want to help Microsoft help you.
Click on Next again…

STEP 16 : Installation Rules

This screen simply checks if there are any processes or other installations running which will stop the installation of SQL Server 2008.

Click on Next again – you’re almost ready to install:

STEP 17 : Ready to Install

This screen summarises what you are about to install and gives you a last chance to cancel or change anything that’s wrongly configured:

Check that what’s being installed is what you want and then click on Install when you’re sure you want to start the installation process:

Installation Progress

SQL Server 2008 will now install. How long it takes depends on the speed of your machine, what load it’s under, the installation media (CD is slower) and what you’ve chosen to install.

…More Installation Progress

… and Finally
Finally, the installation will complete:

…and the following dialog box will appear:

Click on OK, the machine will NOT reboot.
The following will appear:

…followed by:

Click on the Next button again…

STEP 18 : Installation Complete

The following screen appears:

It may be worth clicking on the installation log at the top of the screen to check everything’s gone as expected. Not that this is MUCH smaller than the usual SQL Server installation log files of old.

Finally, click on the Close button. The following dialog will appear:

Click on OK – your server will NOT re-boot at this point.

The dialog box will disappear and you will be returned to the Installation Center:

Click on the Close button (the “x”) in the top right of the screen.
Finally, manually reboot your machine to complete the SQL Server 2008 installation.

Top Tips :

How to check that SQL Server 2008 has installed correctly

Here are a short number of post-installation checks which are useful to perform after re-booting your new SQL Server. You don’t have to run these, and there are other ways to check, but they are very useful for non-DBAs to be sure that the installation is basically sound and a connection can be made to the new SQL Server before handing it over to someone else.

Check 1: Has the SQL Server Service Started?

Check SQL Server 2008 has started.

Check 2: Does Management Studio Work?

Check Management Studio works by firing it up.

Click on NO when you see this dialog box:

Check 3: Can you run a basic query against the new SQL Server?

Check SQL Server works by running a simple query from Management Studio:

Enter the query shown below and hit F5 to run it:

Check 4: Is SQL Server Agent Running?

Check SQL Server Agent is running for scheduled jobs. There should be a green arrow next to the SQL Server Agent database symbol (it’s small, you might have to look hard):

Check 5: Can SQL Server be seen from the Network?

Check that the new SQL Server can be seen from another SQL Server on the same domain by running isql –L (or osql –L):

If you can’t see the new SQL Server in this list, check that the SQL Server Browser service is started on the machine where you have just installed SQL Server.

Check 6: Has the TCP/IP network protocol library been enabled on the server?

If the browser service is started but you still cannot connect to the server, click on Start ->Programs -> SQL Server 2008 -> SQL Server Configuration Manager (on the server where SQL Server’s just been installed)

The SQL Server Configuration Manager window opens.
Click on the SQL Server Network Configuration node and expand it.

In the example below, we have MSSQLSERVER (a base instance of SQL Server), and SQLEXPRESS showing as installed.
If in doubt, click on Protocols for MSSQLSERVER.

In the above screenshot, the TCP/IP network protocol library is disabled. We need to enable it in order that remote servers can talk to the newly installed SQL Server.

  • A word of explanation : In most installations, Named Pipes can be ignored, unless there is a requirement for it. In virtually all environments, VIA can also be ignored as this protocol requires a special network card. Shared memory is the “local” protocol that SQL Server uses when talking to a client application on the same server as itself, for example when SQL Server Management Studio connects to it. It is usually best to leave this enabled.

You will need the TCP/IP protocol enabled if you need to connect to your new SQL Server from a remote client or another server via TCP/IP, which is what most networks use.

If it shows as DISABLED (above), double click on the TCP/IP protocol line, and the following window will appear:

Ensure that Enabled is set to Yes, and click on OK.
The following warning will appear:

Click on OK, and you will be returned to the Configuration Manager window, where TCP/IP will now be shown as enabled:

Go back to the Services applet, and re-start the MSSQLSERVER service so that the TCP/IP protocol can be used to connect to your new SQL Server.

Then try to connect to it again from a remote machine.

If you have experienced problems with the previous connectivity tests, you should now be able to repeat at least some of them successfully.

Advertisements

Writing to a Text File

These examples show various ways to write text to a file.
The first two examples use static methods on the System.IO.File class to write either a complete array of strings or a complete string to a text file.
Example #3 shows how to add text to a file when you have to process each line individually before writing to the file. Examples 1-3 all overwrite all existing content in the file.
Example #4 shows how to append text to an existing file.

c#
class WriteTextFile
{
static void Main()
{

// These examples assume a “C:\Users\Public\TestFolder” folder on your machine.
// You can modify the path if necessary. 

// Example #1: Write an array of strings to a file. 
// Create a string array that consists of three lines. 
string[] lines = {“First line”, “Second line”, “Third line”};
System.IO.File.WriteAllLines(@”C:\Users\Public\TestFolder\WriteLines.txt”, lines);

// Example #2: Write one string to a text file. 
string text = “A class is the most powerful data type in C#. Like structures, ” +
“a class defines the data and behavior of the data type. “;
System.IO.File.WriteAllText(@”C:\Users\Public\TestFolder\WriteText.txt”, text);

// Example #3: Write only some strings in an array to a file. 
using (System.IO.StreamWriter file = new System.IO.StreamWriter(@”C:\Users\Public\TestFolder\WriteLines2.txt”))
{
foreach (string line in lines)
{
if (line.Contains(“Second”) == false)
{
file.WriteLine(line);
}
}
}

// Example #4: Append new text to an existing file 
using (System.IO.StreamWriter file = new System.IO.StreamWriter(@”C:\Users\Public\TestFolder\WriteLines2.txt”, true))
{
file.WriteLine(“Fourth line”);
}
}
}
/* Output (to WriteLines.txt):
First line
Second line
Third line

Output (to WriteText.txt):
A class is the most powerful data type in C#. Like structures, a class defines the data and behavior of the data type.

Output to WriteLines2.txt after Example #3:
First line
Third line

Output to WriteLines2.txt after Example #4:
First line
Third line
Fourth line
*/

Get File Name From a Path

Hi All,
while working on File System, Sometime we need to extract the file name from a given path. In dot Net it is very simple task as Framework library provide a specific class for doing these kind of task. “Path” is the class under the System.IO namespace has various methods for working on path.
GetFileName is the method of this class that extract the File name from the path.

[Visual Basic]
Dim fileName As String = “C:\mydir\myfile.ext”
Dim pathname As String = “C:\mydir\”
Dim result As String
result = Path.GetFileName(fileName)
Console.WriteLine(“GetFileName(‘{0}’) returns ‘{1}'”, fileName, result)
result = Path.GetFileName(pathname)
Console.WriteLine(“GetFileName(‘{0}’) returns ‘{1}'”, pathname, result)

[C#]
string fileName = @”C:\mydir\myfile.ext”;
string path = @”C:\mydir\”;
string result;
result = Path.GetFileName(fileName);
Console.WriteLine(“GetFileName(‘{0}’) returns ‘{1}'”,
fileName, result);
result = Path.GetFileName(path);
Console.WriteLine(“GetFileName(‘{0}’) returns ‘{1}'”,
path, result);

ie10-be-prepared

IE10 – Be Prepared

IE10 will be released as part of Windows 8 in October and will be released later for Windows 7.

When IE10 is released or if you have either the Windows 8 Release Preview or the earlier IE10 Platform Preview, there are at least two things, below, that you need to check at the earliest opportunity.

1) Check your ASP.Net sites run correctly

If you are running ASP.Net sites, check that the servers have been updated with the latest browser information patch. If not they won’t recognise IE10 and will treat it as a ‘down level’ browser and consequently won’t render all the JavaScript that ASP.Net depends on.

It should be obvious if this happening because some ASP.Net functionality (postback events) won’t work.

So for example, if you have a drop down list that triggers something else when the selection changes, this will fail. If in doubt, copy the code below onto a clean page of your own, upload it to your server and open it in IE10 (and another browser for comparison). 

If you find PostBacks failing you’ll need to contact you host company ASAP. If they don’t understand or recognise the issue, refer them to this page.

www.hanselman.com/blog

This explains the issue and has links to the Hotfixes.

2) Switch off compatibility mode for intranet sites

If you locally preview a site that uses HTML5 and CSS3 features (placeholder text, round corners etc.) in IE10, using the EW Development Server or IIS, you may find that these features don’t display.

This is because the default browser mode for intranet sites in IE10 is ‘Compatibility mode’. You can change this in ‘Tools – Compatibility View Settings’ . Uncheck the ‘Display intranet sites in Compatibility View’ option.

Now you’ll notice that there is also a setting ‘Display all websites in Compatibility View’. What happens to your site if a user has this checked, intentionally or unintentionally? Your site won’t display properly.

You can avoid this problem by forcing IE10 into it’s highest or ‘Edge’ mode. You do this by adding the following meta tag to your pages or the DWT / ASP.Net MasterPage.

<meta http-equiv=”X-UA-Compatible” content=”IE=Edge” />

It’s worth adding this to the existing IE Meta Tag snippets in EW V4.

Internet Explorer 10 Compat Inspector

Microsoft has created a ‘simple to use’ JavaScript utility to help detect compatibility issues with IE10. The following user guide shows you how to install it, use it and work with the results.

http://ie.microsoft.com/testdrive/HTML5/CompatInspector/help/post.htm

How to stop ModalPopupExtender-flickering-on-pageload

 If we use the ModalPopupExtender of  Ajax Control Toolkit we may run into flickering issue i.e. the content of ModalPopupExtender shows up for a moment during the page load and then disappears, while it should not be displayed on the page load.To solve this problem we have to set up display property ‘none’ on the pop-up control.As the content of the panel will be shown as popup we have to set the required style there.


<asp:Panel ID=”pnlPicture” runat=”server” CssClass=”modalPopup”  Style=”display:none;”/>

   Now ModalPopupExtender will work perfect for IE but may not work for Firefox. In page load the Modal Popup will not flicker but on a postback or if the page being redirected by a Response.Redirect the Modal Popup will flash. For that we have to set up the style with javascript.
 
function getFlickerSolved()
{
    document.getElementById(‘<%=pnlPicture.ClientID%>’).style.display = ‘none’;
}
 
And we have to call this javascript function on onOkScript/onCancelScript of modalpopupextender or just before the page load.
Code:
<asp:LinkButton ID=”lbtnChangePhoto” runat=”server” Text=”Edit” ToolTip=”Edit Picture”>
</asp:LinkButton>    <!– Clicking on this button The Modalpopup will open –>
 
<asp:Panel ID=”pnlPicture” runat=”server” CssClass=”modalPopup” Style=”display:none;”>
    <p>
        <asp:FileUpload ID=”photoUpload” runat=”server” />
    </p>
    <p>
        <asp:Button ID=”btnUpload” runat=”server” Text=”Upload” OnClick=”btnUpload_Click” onClientClick=”getFlickerSolved();/>”
        <asp:Button ID=”btnHidePopup” runat=”server” Text=”Cancel” />
    </p>
</asp:Panel> <!– The content of this panel will appear as popup –>
 
 <cc1:ModalPopupExtender ID=”modalPopupChangePicture” TargetControlID=”lbtnChangePhoto”PopupControlID=”pnlUploadPicture” runat=”server”
BackgroundCssClass=”modalPopupBackgroundStyle” CancelControlID=”btnHidePopup”onCancelScript=”getFlickerSolved();“>
</cc1:ModalPopupExtender>
 Note: It may not work when “display:none” is in an external stylesheet .It should be in the  Tag.

Google Translator in ASP .Net

Hi Guys,When you need to add Google Translator in you website the this Code will help you.
Capture
Copy paste the below code in .aspx page

<div style=”width: 100%; text-align: left; margin-top: 2px;”>
<div>
<h4 style=”margin: 2px 0px; padding: 0px;”>
View the page in another language</h4>
</div>
<div>
<asp:Panel ID=”Panel1″ runat=”server”>
<div class=”flt_r1″>
<div id=”google_translate_element”>
<div style=”” class=”skiptranslate goog-te-gadget”>
</div>
</div>
<span class=”smallbody”>
<script type=”text/javascript”>
//<![CDATA[
function googleTranslateElementInit() {
new google.translate.TranslateElement({
pageLanguage: ‘en’
}, ‘google_translate_element’);
}
//]]>
</script>
<script src=”http://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit&#8221;
type=”text/javascript”>
</script>
</span>
</div>
</asp:Panel>
</div>
</div>

You can also change the setting from using following Link”

https://translate.google.com/manager/website