Install SQL Server 2008 Standard

Updated: February 25, 2009

After you install Windows Server 2008 Standard on the fourth server and join the server to the domain, you can install SQL Server 2008 Standard. You can use SQL Server 2008 to manage the content database for Windows SharePoint Services and to manage data for line-of-business applications. For more information about installing SQL Server 2008, see “Overview of SQL Server Installation” at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=139828).

To install SQL Server 2008, you must complete the following steps:

  1. Review the installation restrictions related to Windows EBS.

  2. Review the hardware and software requirements.

  3. Review the security considerations for a SQL Server 2008 installation.

  4. Install SQL Server 2008, either by using the Installation Wizard or from the command prompt.

  5. Configure SQL Server 2008 by using graphical and command prompt utilities.

  6. (Optional) Move the Windows SharePoint Services content database to the fourth server.

SQL Server 2008 installation restrictions

Before you deploy SQL Server 2008 in your Windows EBS domain, review the following restrictions:

  • The version of SQL Server 2008 that is included in Windows EBS Premium is licensed for installation only in your Windows EBS network. You cannot install this version of SQL Server 2008 on a server that is not in the Windows EBS domain.

  • The Windows EBS CAL Suite for Premium Users or Devices is required for users or devices that access SQL Server 2008.

  • You can install SQL Server 2008 either on a server running Windows EBS or on the fourth server that you set up for your Windows EBS domain. However, for security reasons, it is recommended that you do not install SQL Server 2008 on a domain controller. It is recommended that you install SQL Server 2008 on the fourth server in the Windows EBS domain.

  • Do not upgrade the instance of SQL Server 2005 Express that is installed on the Management Server and the Security Server, and do not move the databases to the SQL Server Standard Edition that is included in Windows EBS Premium. These types of migrations are not supported.

  • Do not upgrade the instance of the Windows internal database (SQL Server 2005 Embedded Edition) that is installed for Windows Server Update Services and for Windows SharePoint Services (MICROSOFT##SSEE), and do not move the database to the SQL Server Standard Edition that is included in Windows EBS Premium. These types of migrations are not supported.

  • You can download and install Windows SharePoint Services on the Management Server in Windows EBS. You can also install an add-in for the Administration Console to help you administer Windows SharePoint Services in Windows EBS. If the Windows SharePoint Services Add-in for Windows Essential Business Server is installed on the Management Server, you can move the Windows SharePoint Services content database to the fourth server. For information about how to do this, see (Optional) Moving the Windows SharePoint Services content database, later in this document.

    noteNote
    To download an installation package for Windows SharePoint Services 3.0 and the Windows SharePoint Services Add-In for Windows EBS, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=116107).

Hardware and software requirements for SQL Server 2008

You must ensure that your server meets the minimum hardware and software requirements to install and run SQL Server 2008. For more information, see “Hardware and Software Requirements for Installing SQL Server 2008” at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=139829).

Security considerations for the SQL Server 2008 installation

Security is important for every product and every business. By following simple best practices, you can avoid many security vulnerabilities. You should review the security best practices before you install SQL Server 2008. For more information, see “Security Considerations for SQL Server Installation” at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=139831).

Installing SQL Server 2008

To install SQL Server 2008 on the fourth server, perform the following steps:

  1. Log on as a domain administrator. If you do not, the installation is blocked.

  2. Ensure that the fourth server is joined into the Windows EBS domain. If the fourth server is not in the Windows EBS domain, the SQL Server 2008 installation is blocked. You can install only the included version of SQL Server 2008 on a Windows EBS network.

  3. Install SQL Server 2008. For more information, see “Initial Installation (SQL Server 2008)” at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=137358).

Configuring SQL Server 2008

After you install SQL Server 2008, you can further configure SQL Server 2008 by using graphical and command prompt utilities. For more information, see “Configuring SQL Server 2008” at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=139834).

(Optional) Moving the Windows SharePoint Services content database

You can move the content database of Windows SharePoint Services to the instance of SQL Server that is included in Windows EBS Premium. Before you move the database, consider the following:

  • Other than the content database, do not move databases that are associated with Windows SharePoint Services 3.0, such as the configure database or the search database.

  • To move the content database, you must log on to Windows EBS by using an account in the Domain Admin Security Group. Also, at a minimum, you must be assigned the following roles in SQL Server:

    • db_owner   A fixed role that is needed to detach the Windows internal database.

    • dbcreater   A fixed server role that is needed to attach the new SQL Server instance to the Windows internal database.

Complete the following steps to move the Windows SharePoint Services content database.

Step 1.   Prepare your internal Web site

To prepare your internal Web site
  1. Use the Windows SharePoint Services 3.0 tools to remove the content database from the Web application. Removing the content database does not delete it—it only removes the association of the database with the Web application. This action is analogous to detaching a database in SQL Server because the content of the database remains intact.

    1. On the Management Server, click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration.

    2. On the Central Administration page, click the Application Management tab.

    3. In the SharePoint Web Application Management section, click Content databases.

    4. On the Manage Content Databases page, click the content database that you want to move (SharePoint - <Number>). <Number> is a unique identifier that is assigned when the database is created.

    5. On the Manage Content Database Settings page, in the Remove Content Database section, select Remove content database, and then click OK.

  2. Detach the original database from the Windows internal database.

    1. Click Start, click All Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio Express.

    2. In the Connect to Server dialog box, in Server type, select Database Engine, and then, in the Name field, type \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query.

    3. In the Authentication field, select Windows Authentication, and then click Connect.

    4. Click Databases to expand the list, and then click SharePoint - <Number>. <Number> is a unique identifier that is assigned when the database is created.

    5. Right-click the database name, point to Tasks, and then click Detach. The Detach Database dialog box appears.

    6. Click OK.

  3. Copy or move the SharePoint - <Number>.mdf and SharePoint - <Number>_log.ldf files from C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\ to a destination folder on the fourth server.

    noteNote
    The content database files should be stored on the same server where you installed SQL Server.

Step 2.   Attach the database files to SQL Server

To attach the database files to SQL Server
  1. On the fourth server, click Start, and then click All Programs.

  2. Click Microsoft SQL Server 2008, right-click SQL Server Management Studio, and then click Run as administrator.

  3. In the Connect to Server dialog box, select Database Engine as the server type.

  4. In the Server name field, type the server name.

  5. In the Authentication field, click Windows Authentication.

  6. Click Connect.

  7. Right-click Databases, and then click Attach.

  8. In the Attach Database dialog box, click Add. Browse to the location where you transferred the SharePoint - <Number>.mdf and Share - <Number>_log.ldf files, and then select the SharePoint - <Number>.mdf file for the database that you want to attach.

  9. Click OK twice.

Step 3.   Reset the content database

To reset the content database
  1. On the Management Server, click Start, point to Administrative Tools, and then click SharePoint 3.0 Central Administrator.

  2. On the Application Management page, in the SharePoint Web Application Management section, click Content databases.

  3. On the Manage Content Databases page, click Add a content database.

  4. On the Add Content Database page, in the Database Server section, type the exact name of the database instance.

  5. In the Database Name section, type the exact name of the transferred content database (SharePoint - <Number>), and then click OK. You can also reset the content database by using the following commands in a Command Prompt window:

    1. On the drive where Windows SharePoint Services is installed, open a Command Prompt window, and then type cd %COMMONPROGRAMFILES%\Microsoft shared\Web Server Extensions\12\Bin.

    2. Type the following command:

      stsadm –o addcontentdb –url <URL name> -databasename <database name> [-databaseserver <database server name>]

      For the internal Web site, the URL is the one that you assigned when you installed the Windows SharePoint Services Add-in for Windows Essential Business Server, and the database name is SharePoint - <Number>. <Number> is a unique identifier that is assigned when the database is created.

    3. Press ENTER.

  6. On the drive where SharePoint Products and Technologies is installed, open a Command Prompt window, and then type cd %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin. Type the following command:

    Stsadm –o spsearch –action fullcrawlstart

    Press ENTER.

Community Additions

ADD
Show: