Exporter (0) Imprimer
Développer tout

Using SQL Server in Windows Small Business Server 2008 Premium Edition

Windows® Small Business Server 2008 Premium Edition includes 32-bit and 64-bit versions of Microsoft® SQL Server® 2008 Standard Edition for Small Business, which enables you to run line-of-business applications in the Windows SBS 2008 network. SQL Server 2008 Standard Edition for Small Business Server can be installed only in the Windows SBS 2008 network. Because of potential compatibility issues for line-of-business applications, for a limited time, Windows SBS 2008 Premium also includes 32-bit and 64-bit versions of SQL Server 2005 Standard Edition.

noteNote
When the limited time for the inclusion of SQL Server 2005 ends, you are restricted from downgrading the SQL Server component. You are required to upgrade all components all components of the server software to SQL Server 2008 Standard for Small Business.

Installation restrictions

Before you deploy SQL Server in your Windows SBS 2008 domain, be aware of the following restrictions:

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

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

  • You can install SQL Server on the server running Windows SBS 2008 or on the second server that you set up for your Windows SBS 2008 domain. However, for security reasons, it is recommended that you do not install the SQL Server on a domain controller. It is recommended that you install SQL Server on the second server in the Windows SBS 2008 domain. For more information, see Installing SQL Server 2008.

  • Do not upgrade the instance of SQL Server 2005 Express that is installed on the server running Windows SBS 2008 for monitoring (SBSMONITORING), and do not move the database to the SQL Server Standard Edition that is included in Windows SBS 2008 Premium. These types of migration 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 SBS 2008 Premium. These types of migrations are not supported.

  • You can move the Windows SharePoint Services content database to SQL Server Standard Edition. For information about how to do this, see Moving the Windows SharePoint Services content database.

Installing SQL Server 2008

If you plan to install SQL Server 2008 on the second server running Windows SBS 2008 Premium, do the following before you run the installation:

  1. Log on as a domain administrator. If you fail to log on as a domain administrator, the installation is blocked.

  2. Join the second server into the Windows SBS 2008 domain.

  3. If the second server is not in the Windows SBS 2008 domain, the SQL Server 2008 installation is blocked. You can only install the included version of SQL Server 2008 on a Windows SBS 2008 network.

  4. It is recommended that you do not install SQL Server 2008 on a domain controller. If you must install SQL Server 2008 on a server that is a domain controller, you should promote the server as a domain controller prior to installing SQL Server 2008. Do not promote the server as a read-only domain controller. SQL Server 2008 is not supported on read-only domain controllers.

    noteNote
    If you do not promote the server before the installation, SQL Server encounters an access control list (ACL) issue. After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the computer to a domain member.

For information about how to install SQL Server 2008 Standard Edition for Small Business, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125411.

Uninstalling SQL Server 2008

If SQL Server 2008 is installed on Windows SBS 2008 Standard, before you uninstall SQL Server 2008, be aware of the following issues:

  • Do not uninstall SBSMonitoring or Microsoft##SSEE.

  • Do not uninstall the SQL Server Reporting service. This disassociates the certificate that is bound to the IIS Web site. If you encounter this issue, use the following steps to fix it:

    To reinstate the IIS Web site certificate
    1. Open the Windows SBS Console.

    2. At the User Account Control prompt, click Allow.

    3. Click the Network tab, and then click Connectivity.

    4. In the tasks pane, click Fix my network to start the wizard.

    5. When the network is scanned, the following error is displayed: No certificate is bound to the ISS Web site.

    6. Ensure that the check box is selected, and then click Next.

    7. On the wizard completion page, click Finish.

For information about how to uninstall SQL Server 2008 Standard Edition for Small Business Server, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125425.

Installing SQL Server 2005

If you plan to install SQL Server 2005 on the original server running Windows SBS 2008, do the following before you run the installation.

  1. Click Start, click All Programs, click Accessories, and then click Run.

  2. Type regedit, and then click OK.

  3. At the User Account Control prompt, click OK.

  4. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90.

  5. Double-click OriginalMachineName, and then change the OriginalMachineName value name to the current server name.

  6. Click OK.

On the Instance Name page of the original server, do not select SBSMonitoring or Microsoft##SSEE as the instance name because the setup will not upgrade existing instances, which could result in Windows SBS 2008 functionality issues.

If you plan to install SQL Server 2005 on the second server running Windows SBS 2008 Premium Edition, do the following before you run the installation.

  1. Join the second server into the Windows SBS 2008 domain.

  2. It is recommended that you do not install SQL Server 2005 on a domain controller. If you must install SQL Server 2005 on a server that is a domain controller, you should promote the server as a domain controller prior to installing SQL Server 2005. Do not promote the server as a Read-only domain controller. SQL Server 2008 is not supported on Read-only domain controllers.

    noteNote
    If you do not promote the server before the installation, SQL Server encounters an access control list (ACL) issue. After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the computer to a domain member.

For information about how to install SQL Server 2005 Standard Edition for Small Business, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125429.

Uninstalling SQL Server 2005

If SQL Server 2005 is installed on the server running Windows SBS 2008 Standard, before you uninstall SQL Server 2005, be aware of the following issues:

  • Do not uninstall SBSMonitoring or Microsoft##SSEE.

  • Do not uninstall the SQL Server Reporting service. This disassociates the certificate bound to the IIS Web. If you encounter this issue, use the following steps to fix it:

  • During the uninstall, you might encounter a message that says an application needs to be closed before the uninstall can continue. Applications may include SQL Server (#instance name#) or SQL Server Analysis Service (#instance name#). Stop these services before proceeding with the uninstall.

    To stop the services
    1. Click Start, click Administrator Tools, and then click Services.

    2. In the Services list, right-click the service name, and then click Stop.

For information about how to uninstall SQL Server 2005 Standard Edition for Small Business, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125430.

Installing SQL Server on a domain controller

The SQL Server 2008 Standard Edition for Small Business setup does not block installation on a computer that is a domain controller, but the following limitations apply:

  • You cannot run SQL Server services on a domain controller that is running under a local service account or a network service account.

  • After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the computer to a domain controller.

  • After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the computer to a domain member.

  • SQL Server is not supported on a Read-only domain controller.

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 SBS 2008 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.

  • After moving the content database to SQL Server, do not use the task titled “Move Windows SharePoint Services Data,” which is located on the Server Storage tab of the Windows SBS 2008 console. For more information, see Move data using the Detach and Attach components.

  • To complete the SharePoint Services content database move, you must log on to Windows SBS 2008 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   Fixed role needed to detach the Windows internal database.

    • dbcreater   Fixed server role needed to attach the new SQL Server instance to the Windows internal database.

SharePoint Services content database move process

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

Step 1: Prepare your internal Web site

To prepare your internal Web site
  1. To avoid user access to the internal Web site while you are moving data, stop the internal Web site. In the Windows SBS Console, click the Shared Folders and Web Sites tab, click Web sites, and then click Disable this site.

  2. 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. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration.

    2. In the User Account Control prompt, click Continue.

    3. In the Central Administration page, click the Application Management tab.

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

    5. On the Manage Content Databases page, click the content database that you want to move (ShareWebDB).

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

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

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

    2. Right-click SQL Server Management Studio Express, and then click Run as administrator.

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

    4. In the Authentication field, select Windows Authentication, and then click Continue.

    5. Click Databases to expand the list, and then click ShareWebDb.

    6. Right-click the database name, click Tasks, and then click Detach.

      The Detach Database dialog box appears.

    7. Click OK.

  4. Copy or move the ShareWebDb.mdf and ShareWebDb_log.ldf files from %COMMPROGRAMFILES%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\ to a destination folder.

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

Step 2: Create and attach the database files to SQL Server

To create and attach the database files to SQL Server
  1. If you installed SQL Server 2005:

    Log on to the server where you want to install SQL Server to use as the content database.

  2. Install SQL Server 2005 or SQL Server 2008.

  3. If you install SQL Server on a separate server from the server running Windows SBS 2008, you must configure it to allow remote connections.

    1. Enable remote connections on the SQL Server that you want to connect to from a remote computer.

    2. Turn on the SQL Server Browser Service.

    3. Configure the firewall to allow network traffic that is related to SQL Server and to the SQL Server Browser Service.

      For more information, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125442.

  4. If you installed SQL Server 2008:

    1. Start the SQL Configuration Manager, browse to the SQL Server Network Configuration node, and then select SQL Server.

    2. In the right pane, right-click TCP/IP, and then click Enable.

    3. Restart the SQL Browser Service.

    4. To configure services such as Start, Stop, Pause, Restart, and Update service accounts, do the following:

      1. Start the SQL Configuration Manager, browse to SQL Server Services, and then select SQL Server.

      2. In the right pane, right-click the service that you want to change, and then click the appropriate option.

      3. To change the service account, right-click the service, click Properties, and then click the Log On tab.

  5. On the destination server, attach the content database to the SharePoint content database.

    1. Click Start, and then click All Programs.

    2. Click Microsoft SQL Server 2005 or 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, click Tasks, and then click Attach.

    8. In the Attach Database dialog box, click Add. Browse to the location where you transferred the ShareWebDb.mdf and ShareWebDb_log.ldf files, and then select the ShareWebDb.mdf file for the database that you want to attach.

    9. Click OK twice.

Step 3: Reset the content database for the Remote Web Workplace

To reset the database for Remote Web Workplace
  1. If the destination SQL Server instance is on the Windows SBS 2008 server on which the Windows SharePoint Services installed, you can use the SharePoint 3.0 Central Administrator to add the new content database.

    1. Click Start, click 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 (ShareWebDb), and then click OK.

  2. If the destination SQL Server is not on the Windows SBS 2008 server, you might encounter issues when you use the SharePoint 3.0 Central Administrator to add the new content database. To help with this issue, do the following:

    1. Log on to the Windows SBS 2008 server.

    2. On the drive where Windows SharePoint Services is installed, open a Command Prompt window, and then change to the following directory by typing: cd %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.

    3. 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 https://sites.987 and the database name is ShareWebDb.

    4. Press ENTER.

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

    Stsadm –o spsearch –action fullcrawlstart

  4. Press ENTER.

Move data using the Detach and Attach components

After you move the content database to SQL Server, you are no longer able to use the Move Windows SharePoint Services Data task from the Windows SBS Console (Server Storage, which is located on the Backup and Server Storage tab). This is because the task can only move data for the Windows internal database.

If the disk where you are hosting the content database is running out of disk space, you can move the data by using the Detach and Attach components.

For more information about how to do this in SQL Server 2008, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125443.

For more information about how to do this in SQL Server 2005, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125445.

After you move the content database to SQL Server, you can continue to move it to other SQL Server instances as needed. For more information, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=125446.

Cela vous a-t-il été utile ?
(1500 caractères restants)
Merci pour vos suggestions.

Ajouts de la communauté

AJOUTER
Microsoft réalise une enquête en ligne pour recueillir votre opinion sur le site Web de MSDN. Si vous choisissez d’y participer, cette enquête en ligne vous sera présentée lorsque vous quitterez le site Web de MSDN.

Si vous souhaitez y participer,
Afficher:
© 2014 Microsoft