Prerequisites for SQL Server Edition (R2) standalone installation

Original: SQL Server edition (R2) stand-alone installation Prerequisites

Originating From: http://blogs.msdn.com/b/apgcdsd/archive/2012/03/07/sql-server-2008-r2.aspx

When providing technical support to customers, it is found that many of the problems with installing SQL Server (R2) standalone are based on the following typical scenarios, and customers are unaware that this is the prerequisite for SQL Server installation:

1.. NET Framework 3.5 SP1

2. Windows Installer 4.5

3. Visual Studio SP1

4. Setting the region and language in the Control Panel

5. Small Business Install SQL Server (R2) Standard Edition needs to set the domain

6. Installing SQL Server 2008 in Windows Server R2 or Windows 7 with SP1 Consolidated installation mode

1.. NET Framework 3.5 SP1

In Windows Server R2, you should install the. NET Framework 3.5 SP1 in a way that adds Windows features instead of installing it as a standalone component.

In other versions of the Microsoft System, you simply click Install file Setup.exe, which will automatically install the. NET Framework 3.5 SP1 and Windows Installer 4.5.

Running SQL Server 2008 requires the. Net Framework 3.5 SP1 (especially the Express and IA64 editions) and Windows Installer 4.5. After the. Net Framework and the Windows Installer upgrade, you need to restart it to take effect. If you try to install the database again without rebooting the system, you will be prompted to restart with a warning, and you'll choose to have the. Net Framework and Windows installer take effect or exit the installation.

If you choose to cancel, the installer will report a missing installation of Windows Installer 4.5 error. The Setup Wizard bundles the. Net Framework and the installation of Windows Installer, so the two components are installed at the same time. Once the prerequisites are installed (and the system has been restarted), the installation Guide runs the SQL Server installation Center.

Of course, you can also install these prerequisites separately. However, it is recommended to install using the Installation Wizard to avoid restarting the system multiple times. Because the two components are bundled, a single reboot is required.

Automatically run Setup.exe (or manually double-click setup.exe), the following window will pop up:

When you agree to the license terms, the. Net 3.5 SP1 installation will continue. The splash screen will show that the component is being downloaded, in fact only copied from the DVD. This process takes some time (about 10-20 minutes, depending on the hardware condition).

If the SQL Server Setup Wizard fails to install the. NET Framework 3.5 SP1, and the above error pops up, you can install it manually. The installation media is included on the DVD and you do not need to download it from the network.

2. Windows Installer 4.5

Agree to the license Treaty.

Additional prerequisites are listed under the "Hardware and software Conditions" topic in Books Online.

In 2003, the following window will pop up:

In Vista and Windows Server 2008, this is the case:

Installs the update and requires only one reboot for the update to take effect.

Installation with the Installation Wizard requires only one reboot, and two components per installation will require two reboots. For more information, please refer to Bob Ward's blog in the previous section.

3. Visual Studio SP1

This step of the update is important when you have installed Visual Studio 2008. Because this step is not integrated into the installation Wizard, you need to download the installation package from the network. But this update is not required, only if you need to install SSIS, BIDS or Management tools. Therefore, this step occurs as part of component detection rather than as part of a global system configuration check.

More information:

Visual Studio SP1 Download Link: http://www.microsoft.com/download/en/details.aspx?id=10986 or http://www.microsoft.com/download/en/details.aspx?id=13276 For more information for this topic, see: http://blogs.msdn.com/psssql/archive/2008/08/11/ Sql-server-2008-visual-studio-2008-sp1-and-net-framework-3-5-sp1-explained.aspx

4. Regional and Language settings

When you install a localized version of SQL Server R2, but your Windows has a different language setting, you encounter the above error back:

The workaround for this problem is to align the operating system language settings with the language of SQL Server in Control Panel:

Change operating system user interface settings

1. Install the MUI for the operating system that matches the localized version of SQL Server (if it is not already installed).

2. In the Control Panel, open the regional and Language Options.

3. On the Languages tab, select a value from the list for Language used in menus and dialogs.

4. This setting affects the user interface language of SQL Server, so it must match the localized version of SQL Server.

5. Click Apply to confirm the change, and then click OK to close the window

To change the operating system user locale

1. Install the MUI for the operating system that matches the localized version of SQL Server (if it is not already installed).

2. In the Control Panel, open the regional and Language Options.

3. On the Regional Options tab, select a value from the list for select an item to match its preferences. This setting affects the culture-specific data format.

4. Click Apply to confirm the change, and then click OK to close the window.

Change system locale Settings

1. Install the MUI for the operating system that matches the localized version of SQL Server (if it is not already installed).

2. In the Control Panel, open the regional and Language Options.

3. On the Advanced tab, from the list, Select a language to match the language version of the Non-unicode programs your want to use Select a value. This setting enables SQL Server Setup to select the best default collation for the SQL Server installation.

4. Click Apply to confirm the change, and then click OK to close the window.

5. Integrated Installation

Because SQL Server is published before Windows Server R2 and Windows 7, it does not recognize these versions. To solve this problem, starting with SP1, you can integrate the update with the original media as a PCU package.

More information:

For more information for this topic, see: Http://blogs.msdn.com/b/petersad/archive/2009/02/25/sql-server-2008-creating-a-merged-slisptream-drop.aspx

1. Download the service pack package that matches your system architecture. If your system is an X x64-based system, for example, download the package for SQL Server Service Pack 1 x 64.
   • Extract the service pack by running the following command:

Sqlserver2008sp1-kb968369-x64-enu.exe/x:c:\sp1

2. Run the Setup.exe file from the source media by specifying SQL Server 2008 in the /pcusource parameter.

Setup.exe/pcusource=c:\sp1

6. Some limitations of installing SQL Server R2 Standard Edition for Small Business

If you install SQL Server R2 Standard Edition for Small business, and your machine is not in the domain, you will encounter such an error " Operating System supported for edition ". To solve the issue, you should add your computer into one of the your company's domain or create a new domain by "DCPROMO". It has limitation for the domain to install SQL Server.

Windows Small Business Server 2011 Premium Edition includes SQL Server r2http://www.microsoft.com/sbs/en/us/ Editions-overview.aspx. This version has the same features as the Standard Edition. The difference is that SQL Edition SBS standard is a special Standard Edition, which is a version of Small Business Server, which is part of the small and medium Enterprise Suite, only and the corresponding SMB Suite edition of Windows Small Business Installation and use from Server 20,081.

The following conditions are required for the SQL Server SBS version:

1. This version of SQL Server can only be installed in:

? Windows Server Standard

? Windows Server standard without Hyper-V

? Windows Small Business Server 2008

? Windows Server for Windows Essential server Solutions

? Windows Server without Hyper-V for Windows Essential Server Solutions

Please note : SQL Server R2 standard for small business is available for installation on Windows Server Enterprise, but SQL Server Standa RD for Small business is not allowed.

2. Windows server must be joined to a domain and is the root of active Directory forest

3. Trust relationship does not exist for this domain and other domains

4. The domain cannot have any subdomains

5. The sum of users and devices in this domain does not exceed 75

6. Customers cannot run SQL Server software with the same serial number on other operating systems in the domain at the same time

If the check fails, you may see the following message: "Operating System supported for Edition" topic.

Clicking in the Failed status shows the following message:

---------------------------
Rule Check Result
---------------------------
Rule "Operating System supported for edition" failed.
This SQL Server edition are not supported on the this operating system. See SQL Server
Books Online for information on supported operating systems for SQL Small
Business Server Edition.
---------------------------

If you find that your server is not in any domain, the most straightforward solution to this problem is to use start-and-run->dcpromo to create a new domain for him. Other machines that need to connect to SQL Server do not need to be in this domain.

Prerequisites for SQL Server Edition (R2) standalone installation