Export (0) Print
Expand All

Installing SQL Server 2005 WorkGroup Edition in Windows Small Business Server 2003 R2

Updated: May 27, 2009

Applies To: Windows SBS 2003

In this document:

noteNote
The information in this document applies to Windows SBS 2003 R2, Premium Edition. You can also use these installation instructions to install Microsoft SQL Server™ 2005 Workgroup Edition on a computer that is running Windows SBS 2003 Premium Edition, with Service Pack 1 (SP1). However, the software included with Windows SBS 2003 Premium Edition, with SP1, does not include SQL Server 2005. You need to purchase a separate copy of SQL Server 2005 if you want to install it on a computer that is running Windows SBS 2003 Premium Edition with SP1.

After you complete the Windows SBS 2003 SP1 installation portion of Windows SBS 2003 R2 Setup, you can use the Premium Technologies discs to install SQL Server 2005.

If you want to be able to search document libraries on your company's internal Web site by using full-text search, you can migrate the instance of Microsoft SQL Server 2000 Desktop Engine (Windows) (WMSDE) that is used by Microsoft Windows SharePoint® Services to SQL Server 2005. Additionally, you can install SQL Server 2005 as your database for a business application.

Before you install SQL Server 2005, review the following points:

  • Do not migrate the instance of MSDE that is installed for Monitoring (MSSQL$SBSMONITORING), because this is not supported.

  • Do not migrate the instance of WMSDE that is installed for Windows SBS 2003 R2 Update Services (MSSQL$WSUS), because this is not supported on Windows SBS 2003 at this time.

  • Do not migrate the instance of MSDE that is installed for Internet Security and Acceleration (ISA) Server 2004 (MSSQL$MSFW), because this is not supported on Windows SBS 2003 at this time.

  • If you are installing a new instance of SQL Server and you have an existing SQL Server installation, or if you are installing SQL Server in a language that is different from the language that is used by the client computers that are connecting to the database, or if you have an application that depends on settings from a previous version of SQL Server, you must complete a custom Setup and specify collation settings. For information about collation settings, see "SQL Server Collation Settings" later in this document.

  • To review the SQL Server 2005 release notes, open D:\SQL2005\ReadMeSql2005.htm on Premium Technologies Disc 1, where D is the letter of your CD drive.

ImportantImportant
You must be logged on to the Administrator account or another account that is a member of the Domain Admins security group to install SQL Server 2005.

Migrate the SHAREPOINT Instance of WMSDE

Before you begin the migration, you must prepare the http://companyweb Web site.

To prepare the http://companyweb Web site
  1. Stop the http://companyweb Web site. To do so, click Start, and then click Server Management. In the Server Management console pane, double-click Advanced Management, double-click Internet Information Services, double-click ServerName(local computer), and then double-click Websites, where ServerName is the name of your server computer. Right-click companyweb, and then click Stop.

  2. Stop the SharePoint Timer Service. To do so, click Start, point to Administrative Tools, and then click Services. Double-click SharePoint Timer Service to open the Properties dialog box. On the General tab, click Stop. Choose Manual for the Startup Type. Click OK to apply the changes and to close the SharePoint Timer Services Properties dialog. Leave Services open for the next step.

  3. Stop the MSSQL$SHAREPOINT service. While still in Services, right-click MSSQL$SHAREPOINT, and then click Stop.

  4. Back up the Windows SharePoint Services database files. To do so, browse to %SystemDrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data, and then copy the following files to a backup location of your choosing:

    • STS_ServerName_1.mdf

    • STS_Config.mdf

    • STS_ServerName_1.mdf_log.LDF

    • STS_Config_log.LDF

    where ServerName is the name of your server.

    noteNote
    By default, the SHAREPOINT WMSDE database files are installed in %SystemDrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data. However, you may have installed the database files in a different location.

    noteNote
    If the original copies of these files become corrupted or overwritten, you need to use the backup copies to reattach to the SHAREPOINT instance of SQL Server 2005 that you create later in this document. In order to successfully reattach the backup copies to the database, you must copy the backup copies of the above database files back to %SystemDrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data.

  5. Remove the SHAREPOINT WMSDE instance. Click Start, point to Control Panel, and then click Add or Remove Programs. Select Microsoft SQL Server Desktop Engine (Sharepoint), and then click Remove. Click Yes to confirm that you want to delete MSDE (SharePoint). You must restart the computer before you continue with the following procedures.

To create the SQL Server 2005 Workgroup Edition SHAREPOINT instance
  1. From the Autorun page of Premium Technologies Disc 1 (D:\Setup.exe, where D is the letter of your CD drive), click Install Microsoft SQL Server 2005.

    noteNote
    If Windows SBS 2003 R2 was preinstalled on your server, your original equipment manufacturer (OEM) might have created a shortcut on the desktop for installing SQL Server 2005.

  2. On the End User License Agreement page, review the licensing agreement. To continue, you must accept the agreement.

  3. On the Installing Prerequisites page click Install. SQL Server 2005 Setup installs the components that are required for SQL Server setup. When it finishes installing them, click Next.

  4. On the Welcome to the Microsoft SQL Server Installation Wizard page, click Next.

  5. On the System Configuration Check page, verify that you have no potential installation problems, then click Next.

  6. If this is the first instance of SQL Server 2005 that you are installing, the Registration Information page appears. By default, Setup automatically enters the product key for you. Enter your Name and Company information, and then click Next.

  7. On the Feature Selection page, click SQL Server Database Services and then click Entire feature will be installed on local hard drive. Expand SQL Server Database Services and ensure that all sub-features, including Full-Text Search, are set to install.

  8. While still on the Feature Selection page, expand Client Components, click Management Tools, and then click Entire feature will be installed on local hard drive. By default, Setup also selects Connectivity Components and SQLXML Client Features for installation. Click Next.

    ImportantImportant
    If this is not the first instance of SQL Server 2005 that is installed on the server, and you did not install the Client Components with your first SQL Server 2005 instance, you may be unable to install Client Components when migrating the WMSDE SHAREPOINT instance to full SQL Server 2005. SQL Setup may prompt you with a message that the Client Components have already been installed.

    To work around this issue, complete the WMSDE SHAREPOINT migration, and then click Start. Point to Control Panel, and then click Add or Remove Programs. In Add or Remove Programs, click Microsoft SQL Server 2005, and then click Change. In Component Selection, click Workstation Components under SQL Server 2005 Common Components, and then click Next. Follow the SQL Setup Wizard until the Change or Remove Instance page. Click Change Installed Components. Under Client Components, click Management Tools, and then click Entire feature will be installed on local hard drive. Click Next to continue, and then complete the wizard.

  9. On the Instance Name page, click Named instance. In the Named instance box, type SHAREPOINT.

    CautionCaution
    You must type the instance name that is shown, in uppercase letters. If the instance name is not in uppercase letters, the migration to SQL Server 2005 Workgroup will fail.

  10. On the Service Account page, click Use the built-in System account, and then click Local system for the account. Click Next.

  11. On the Authentication Mode page, choose Windows AuthenticationMode. Click Next.

  12. On the Collation Settings page, accept the default of Dictionary order, case-insensitive, for use with 1252 Character Set for SQL collations (used for compatibility with previous versions of SQL Server). Click Next.

  13. When the Error and Usage Report Settings page appears, you can choose to automatically send error reports to Microsoft or to your corporate error-reporting server. You can also choose to send data about feature usage for SQL Server 2005 to Microsoft. Click Next.

  14. On the Ready to Install page, click Install.

  15. When SQL Server 2005 Setup prompts you to "Please insert Disc 2," insert Premium Technologies Disc 2, and then click OK.

  16. Click Next when that button becomes available on the Setup Progress page.

  17. On the Completing Microsoft SQL Server 2005 Setup page, click Finish.

To configure permissions for the new SHAREPOINT instance of SQL Server 2005
  1. Open SQL Server Management Studio. Click Start, point to All Programs, point to Microsoft SQL Server 2005 and then click SQL Server Management Studio.

  2. On the Connect to Server page, ensure that Server type: is set to Database Engine and that Server name: is set to ServerName\SHAREPOINT, where ServerName is the name of your server. Click Connect.

  3. In the Object Explorer pane, expand ServerName\SHAREPOINT (SQL Server 9.0.1399 - DomainName\administrator), where DomainName is the name of your Windows SBS domain.

  4. Double-click Security, right-click Logins, and then click New Login.

  5. In Login name, type NT Authority\Network Service, and then click OK.

    ImportantImportant
    If you are running the Dutch, Portuguese (Brazil), or Swedish versions of Windows SBS 2003 R2 Premium Edition, you must enter the translation of the NT Authority\Network Service account name.

    noteNote
    Do not click Search after typing NT Authority\Network Service, because SQL Server Management Studio will not find the NT Authority\Network Service account. If you have incorrectly entered the service name, you receive an error message after you click OK.

  6. Repeat steps 4 and 5 to add the DomainName\SBS SP Admins group as a new login.

  7. In the Object Explorer pane, expand Logins, and then double-click the NT Authority\Network Service account.

  8. On the Login Properties page for NT Authority\Network Service, under Select a page, click Server Roles.

  9. Under Server roles, select the dbcreator and securityadmin roles. Click OK.

  10. Keep Microsoft SQL Server Management Studio open for the next procedure.

ImportantImportant
If you are running the Dutch, Portuguese (Brazil), or Swedish versions of Windows SBS 2003 R2 Premium Edition, you need to complete the following procedure in order to set the default full-text language before you finish attaching the databases to the new SHAREPOINT SQL Server 2005 instance. If you are not running the Dutch, Portuguese (Brazil), or Swedish versions of Windows SBS 2003 R2 Premium Edition, skip to the procedure "To attach the database files to the new SHAREPOINT instance of SQL Server 2005."

Dutch, Portuguese (Brazil), or Swedish installations only
  1. While you are still in Microsoft SQL Server Management Studio, right-click ServerName\SHAREPOINT (SQL Server 9.0.1399 - DomainName\administrator), where DomainName is the name of your Windows SBS domain, and then click Properties.

  2. In the Server Properties page, under Select a page, click Advanced.

  3. Under Miscellaneous advanced properties, locate Default Full-Text Language. Highlight the current value and replace it with the language code that corresponds to your language. The language code for Dutch is 1043. For Swedish, it is 1053. For Neutral, it is 0. For Portuguese (Brazil), use Neutral because there is no language code for Portuguese (Brazil).

  4. Click OK.

  5. You are now ready to continue with the next procedure and attach the database files to the new SHAREPOINT instance of SQL Server 2005.

To attach the database files to the new SHAREPOINT instance of SQL Server 2005
  1. While still in Microsoft SQL Server Management Studio, in Object Explorer , expand ServerName\SHAREPOINT (SQL Server 9.0.1399 - DomainName\administrator), where DomainName is the name of your Windows SBS domain.

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

  3. On the Attach Databases page, click Add.

  4. Browse to %SystemDrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data, select STS_ServerName_1.mdf and then click OK.

  5. On the Attach Databases page, click OK. The action finishes and Object Explorer in Microsoft SQL Server Management Studio appears.

  6. Repeat step 2 through 5 to attach the STS_Config.mdf database file.

  7. Restart the Windows SharePoint Timer Service by clicking Start, pointing to Administrative Tools, and then clicking Services. Right-click SharePoint Timer Service, and then click Properties. On the General tab, select Automatic for the Startup Type. Click Start to start the service, and then click OK to close the SharePoint Timer Service Properties dialog box.

  8. Close Services.

  9. Restart http://companyweb by clicking Start and then clicking Server Management. In the Server Management console, double-click Advanced Management, double-click Internet Information Services, double-click ServerName (local computer), and then double-click Websites. Right-click companyweb, and then click Start.

To turn on full-text search in Windows SharePoint Services
  1. Click Start, point to Administrative Tools, and then click SharePoint Central Administration.

  2. In Component Configuration, click Configure full-text search.

    noteNote
    If you encounter the error message, “Configuration database can’t be found,” ensure that the SQL Server (SHAREPOINT) service is started. To do so, click Start, point to Administrative Tools, and then click Services. If the service is not started, right-click the service name, and then click Start. Click OK to exit Services.

  3. Select the Enable full-text search and index component check box, and then click OK.

Migrate a SHAREPOINT Instance of SQL Server 2000

The steps to migrate the SHAREPOINT SQL Server 2000 instance are nearly identical to the steps to migrate the SHAREPOINT WMSDE instance to SQL Server 2005 Workgroup Edition. Use the following procedure to migrate the SHAREPOINT SQL Server 2000 instance to SQL Server 2005 Workgroup Edition.

To migrate the SHAREPOINT SQL Server 2000 instance to SQL Server 2005 Workgroup Edition
  1. Complete the procedure "To prepare the http://companyweb Web site," earlier in this document. Note that you must uninstall SQL Server 2000 by using Add or Remove Programs, not WMSDE.

    ImportantImportant
    Before you uninstall SQL Server 2000, review Article 920899 in the Microsoft KnowledgeBase (http://go.microsoft.com/fwlink/?LinkId=68562). The article addresses known issues with uninstalling SQL Server 2000 with Service Pack 4.

  2. Complete the procedure "To create the SQL Server 2005 Workgroup Edition SHAREPOINT instance," earlier in this document, to complete a new installation of SQL Server 2005 for Windows SharePoint Services.

  3. Complete the procedure "To configure permissions for the new SHAREPOINT instance of SQL Server 2005".

  4. If you are installing the Dutch, Swedish, or Portuguese (Brazil) versions of Windows SBS 2003 R2 Premium Edition, complete the procedure "Dutch, Portuguese (Brazil), or Swedish installations only," earlier in this document. Otherwise, skip this step.

  5. Complete the procedure "To attach the database files to the new SHAREPOINT instance of SQL Server 2005."

  6. If you enabled full-text searching for Windows SharePoint Services when you upgraded the SHAREPOINT WMSDE to SQL Server 2000, you do not have to enable it again after migrating to SQL Server 2005. If you did not enable full-text searching previously, follow the steps provided in the procedure "To turn on full-text search in Windows SharePoint Services," earlier in this document.

Install a New Instance of SQL Server 2005 Workgroup Edition

ImportantImportant
Follow the instructions in this section to install an instance of SQL Server 2005 on your server. If SQL Server 2000 is already installed and you want to use the same instance name for your SQL Server 2005 installation, you need to perform a migration.

For more information, see "Migrate a SQL Server 2000 instance to SQL Server 2005 Workgroup Edition," later in this document.

To install a new instance of SQL Server 2005 Workgroup Edition
  1. From the Autorun page of the Premium Technologies disc (D:\Setup.exe, where D is the letter of your CD drive), click Install Microsoft SQL Server 2005.

    noteNote
    If Windows SBS 2003 R2 was preinstalled on your server, your original equipment manufacturer (OEM) might have created a shortcut on the desktop for installing the Premium Technologies.

    noteNote
    If you are installing this instance of SQL Server 2005 Workgroup Edition for use with a line-of-business application, consult the application's documentation to ensure compatibility with SQL Server 2005 as well as to determine any specific configuration requirements.

  2. On the End User License Agreement page, review the licensing agreement. To continue, you must accept the agreement.

  3. On the Installing Prerequisites page, SQL Server 2005 Setup installs the components that SQL Server Setup requires. When Setup has finished installing the required components, click Next.

  4. On the Welcome to the Microsoft SQL Server Installation Wizard page, click Next.

  5. On the System Configuration Check page, verify that you have no potential installation problems, then click Next.

  6. If this is the first instance of SQL Server 2005 that you are installing, the Registration Information page appears. By default, Setup automatically enters the product key for you. Enter your Name and Company information, and then click Next.

  7. On the Feature Selection page, click the icon next to SQL Server Database Services, and then click Entire feature will be installed on local hard drive. If it is not already expanded, expand Client Components. Click the icon next to Management Tools, and then click Will be installed on local hard drive. Ensure that Connectivity Tools are also selected for installation. Click Next.

    ImportantImportant
    If your line-of-business (LOB) application requires you to install the Microsoft SQL Server 2005 Reporting Services component, do not select it for installation at this time. Instead, complete your SQL Server 2005 installation, and then follow the steps in the procedure "To install SQL Server 2005 Reporting Services," later in this document.

  8. On the Instance Name page, click Default instance.

    ImportantImportant
    If you are installing SQL Server 2005 as part of your LOB installation, consult the technical information for the LOB application in order to determine whether you need to create a named instance of SQL Server 2005 other than the Default instance.

  9. On the Service Account page, click Use the built-in System account, and then choose Local system for the account.

  10. On the Authentication Mode page, choose Windows AuthenticationMode.

  11. On the Collation Settings page, accept the default of Dictionary order, case-insensitive, for use with 1252 Character Set for SQL collations (used for compatibility with previous versions of SQL Server).

  12. When the Error and Usage Report Settings page appears, you can choose to automatically send error reports to Microsoft or to your corporate error-reporting server. You can also choose to send data about feature usage for SQL Server 2005 to Microsoft. Click Next.

  13. On the Ready to Install page, click Install.

  14. When SQL Server 2005 Setup prompts you to "Insert Disc 2," insert Premium Technologies Disc 2, and then click OK.

  15. Click Next when that button becomes available on the Setup Progress page.

  16. On the Completing Microsoft SQL Server 2005 Setup page, click Finish.

  17. If your LOB application does not require you to install SQL Server 2005 Reporting Services, then skip the next procedure, "To install SQL Server 2005 Reporting Services."

To install SQL Server 2005 Reporting Services
  1. After you complete Setup for SQL Server 2005, restart Setup from the Premium Technologies Autorun screen. To do so, insert Premium Technologies Disc 1 into your CD drive, and then click Install Microsoft SQL Server 2005. Continue through the SQL Server 2005 Setup Wizard and accept the defaults.

    noteNote
    If Windows SBS 2003 R2 was preinstalled on your server, your original equipment manufacturer (OEM) might have created a shortcut on the desktop for installing SQL Server 2005.

  2. On the Feature Selection page, click the icon next to Reporting Services, and then click Entire feature will be installed on local hard drive. Click Next.

  3. On the Instance Name page, select the instance name that will use Reporting Services. Click Next.

  4. On the Existing components page, click Next.

  5. On the Service Account page, use the service account that you used during SQL Server 2005 Setup. Click Next.

  6. On the Report Server Installation Options page, click Next.

  7. To finish installing SQL Server 2005 Reporting Services, continue through the Setup Wizard, accepting the defaults.

ImportantImportant
After you finish installing Reporting Services, you must run the Reporting Services Configuration Manager to fully configure and enable Reporting Services. Consult the technical information for your LOB application to determine the specific configuration settings.

To open the Reporting Services Configuration Manager, click Start, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click Reporting Services Configuration.

ImportantImportant
If you want to install Reporting Services and you have Microsoft Internet Security and Acceleration (ISA) Server 2004 installed, see Article 920803 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=68563). The article addresses a known issue with Reporting Services and ISA Server 2004.

Migrate a SQL Server 2000 Instance to SQL Server 2005 Workgroup Edition

If you are using an existing SQL Server 2000 instance with your LOB application and you want to move the instance to SQL Server 2005, you need to perform a migration. For more information about how to perform this migration, consult the technical information for your LOB application.

ImportantImportant
Before uninstalling SQL Server 2000, see Article 920899 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=68562). The article addresses known issues with uninstalling SQL Server 2000 with Service Pack 4.

SQL Server Collation Settings

It is recommended that you use the default settings for installing SQL Server, unless you need to specify collation settings. You must specify a collation setting if you meet one of the following criteria:

  • You are using a business application that depends on settings from a previous version of SQL Server. Check the documentation for your business application to verify which collation settings are required.

  • You must match the Windows locale of another computer, or you must match the collation settings of another instance of SQL Server. If SQL Server is in a language that is different from the client computers that are connecting to the database, you must specify a Collation Designator and then select the name of a specific Windows collation from the list. You can then specify a Sort Order option to use with the selected Collation Designator.

  • If you are unsure about which collation settings to use, click Help on the Collation Settings page, and then click Windows Collation Designators. If you are unsure of the sort order, click Windows Collation Sorting Styles in Help.

To verify the Windows locale of another computer
  1. On the other computer, click Start, click Run, and then type Control to open Control Panel.

  2. Double-click Regional Options (also called Regional Settings or Regional and Language Options). A dialog box appears.

  3. Note whether the locale of the other computer is different from the locale of your computer that is running Windows Small Business Server. If the locale differs, use the table in the "Windows Collation Designators" Help file to find the corresponding Collation Designator.

  • The collation settings must match those of another SQL Server installation. To match an earlier version of SQL Server, select SQL Collations (used for backward compatibility with previous versions of SQL Server). The default setting for the locale of your operating system appears in the collation settings list box.

It is important to consider the following information about collation settings:

  • Many server-to-server activities can fail if the collation settings are not consistent across servers.

  • You can change collation settings after you run Setup, but you must rebuild the databases and reload the data.

  • It is recommended that you verify the necessary selections for Collation Designator and Sort Order with the collation settings for the other installation of SQL Server.

To verify collation settings
  1. From the computer that is running SQL Server, open SQL Server Management Studio (click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio).

  2. In the Connect to Server dialog box, select Database Engine for Server type, select the name of the SQL Server instance for which you want to verify the collation settings, and then specify the authentication information for the connection.

  3. In the Object Explorer, right-click the SQL Server instance and click New Query.

  4. In the query pane, type the following:

    sp_helpsort 
    go 
    
  5. Press Ctrl+T to show results in text, and then press F5 to run the commands.

  6. The default collation settings of your server appear in the results pane of the query window.

Copyright

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.

© 2006 Microsoft Corporation. All rights reserved.

Microsoft, Windows, and SharePoint are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft