Install SQL Server 2008 R2 (Setup) The SQL Server Installation Wizard provides a single feature tree for

installation of all SQL Server components so that you do not have to install the following components individually: • Database Engine • Analysis Services • Reporting Services • Integration Services • Replication • Management tools • Connectivity components • Sample databases, samples, and SQL Server Books Online Note SQL Server Compact runtime and query tools are installed when you install SQL Server Management Studio and SQL Server Integration Services. SQL Server Compact Server tools are installed if you create a replication subscription involving SQL Server Compact. These additional topics document other ways to install SQL Server: • How to: Install SQL Server 2008 R2 from the Command Prompt. • How to: Create a New SQL Server Failover Cluster (Setup). • How to: Upgrade to SQL Server 2008 R2 (Setup). Prerequisites Before you install SQL Server, review topics in Planning a SQL Server Installation. Before you install SQL Server 2008 R2 side by side with one or more SQL Server 2008 instances, see Considerations for Side-by-Side Instances of SQL Server 2008 R2 and SQL Server 2008. Note For local installations, you must run Setup as an administrator. If you install SQL Server from a remote share, you must use a domain account that has read and execute permissions on the remote share. Note You may need to apply cumulative updates to the original media before you install SQL Server 2008 R2, if you are affected by a known issue in the setup program. For more information about known issues and detailed instructions, see How to update SQL Server 2008 R2 Setup by running a newer version of the SQL Server 2008 R2 Setup support files.

To install SQL Server 2008 R2
1. Insert the SQL Server installation media. From the root folder, double-click Setup.exe. To install from a network share, locate the root folder on the share, and then double-click Setup.exe. If the Microsoft SQL Server 2008 Setup dialog box appears, click OK to install the prerequisites, then click Cancel to exit SQL Server installation. 2. If the .NET Framework 3.5 SP1 installation dialog box appears, select the check box to accept the .NET Framework 3.5 SP1 License Agreement. Click Next. To exit SQL Server installation, click Cancel. When installation of .NET Framework 3.5 SP1 is complete, click Finish. 3. Windows Installer 4.5 is also required, and might be installed by the Installation Wizard. If you are prompted to restart your computer, restart it, and then restart SQL Server Setup.exe. 4. When the prerequisites are installed, the Installation Wizard runs the SQL Server Installation Center. To create a new installation of SQL Server, click New Installation or Add Features to an Existing Installation. 5. The System Configuration Checker runs a discovery operation on your computer. To continue, click OK. If Setup detects SQL Server 2008 on the machine, you will see a warning about the automatic upgrade of shared components to SQL Server 2008 R2. For more information about side-by-side instances of SQL Server 2008 R2 and SQL Server 2008, see Considerations for Side-by-Side Instances of SQL Server 2008 R2 and SQL Server 2008. Setup log files are created for your installation. For more information, see How to: View and Read SQL Server Setup Log Files. 6. On the Language Selection page, you can specify the language for your instance of SQL Server if you are installing on a localized operating system and the installation media includes language packs for both English and the language corresponding to the operating system. For more information about cross-language support and installation considerations, see Local Language Versions in SQL Server. To continue, click Next. 7. On the Product Key page, select an option button to indicate whether you are installing a free edition of SQL Server, or a production version of the product that has a PID key. For more information, see Editions and Components of SQL Server 2008 R2. 8. On the License Terms page, read the license agreement, and then select the check box to accept the license terms and conditions. To help improve SQL Server, you can also enable the feature usage option and send reports to Microsoft. 9. The System Configuration Checker verifies the system state of your computer before Setup continues. 10.On the Feature Role page, select SQL Server Feature Installation, and then click Next to continue to the Feature Selection page. 11.On the Feature Selection page, select the components for your installation. A description for each component group appears in the right pane after you select the feature name. You can select any combination of check boxes. For more information, see Editions and Components of SQL Server 2008 R2. You can also specify a custom directory for shared components by using the field at the bottom of the Feature Selection page. To change the installation path for shared components, either update the path in the field at the bottom of the dialog box, or click Browse to move to an

installation directory. The default installation path is C:\Program Files\Microsoft SQL Server00\. 12.On the Instance Configuration page, specify whether to install a default instance or a named instance. For more information, see Instance Configuration. Click Next to continue. Instance ID — By default, the instance name is used as the Instance ID. This is used to identify installation directories and registry keys for your instance of SQL Server. This is the case for default instances and named instances. For a default instance, the instance name and instance ID would be MSSQLSERVER. To use a nondefault instance ID, select the Instance ID check box and provide a value. Note Typical stand-alone instances of SQL Server 2008 R2, whether default or named instances, do not use a nondefault value for the Instance ID check box. Instance root directory — By default, the instance root directory is C:\Program Files\Microsoft SQL Server00\. To specify a nondefault root directory, use the field provided, or click Browse to locate an installation folder. All SQL Server service packs and upgrades will apply to every component of an instance of SQL Server. Detected instances and features — The grid shows instances of SQL Server that are on the computer where Setup is running. If a default instance is already installed on the computer, you must install a named instance of SQL Server 2008 R2.

13.The Disk Space Requirements page calculates the required disk space for the features that you specify. Then it compares the required space to the available disk space. For more information, see Disk Space Requirements. 14.Work flow for the rest of this topic depends on the features that you have specified for your installation. You might not see all the pages, depending on your selections. 15.On the Server Configuration — Service Accounts page, specify login accounts for SQL Server services. The actual services that are configured on this page depend on the features that you selected to install. You can assign the same login account to all SQL Server services, or you can configure each service account individually. You can also specify whether services start automatically, are started manually, or are disabled. Microsoft recommends that you configure service accounts individually to provide least privileges for each service, where SQL Server services are granted the minimum permissions they have to have to complete their tasks. For more information, see Server Configuration - Service Accounts and Setting Up Windows Service Accounts. To specify the same logon account for all service accounts in this instance of SQL Server, provide credentials in the fields at the bottom of the page. Security Note Do not use a blank password. Use a strong password. When you are finished specifying login information for SQL Server services, click Next. 16.Use the Server Configuration — Collation tab to specify nondefault collations for the Database Engine and Analysis Services. For more information, see Server Configuration - Collation. 17.Use the Database Engine Configuration - Account Provisioning page to specify the following: • Security Mode — select Windows Authentication or Mixed Mode Authentication for your instance of SQL Server. If you select Mixed Mode Authentication, you must provide a strong password for the built-in SQL Server system administrator account. After a device establishes a successful connection to SQL Server, the security mechanism is the same for both Windows Authentication and Mixed Mode. For more information, see Database Engine Configuration - Account Provisioning. • SQL Server Administrators — You must specify at least one system administrator for the instance of SQL Server. To add the account under which SQL Server Setup is running, click Add Current User. To add or remove accounts from the list of system administrators, click Add or Remove, and then edit the list of users, groups, or computers that will have administrator privileges for the instance of SQL Server. For more information, see Database Engine Configuration - Account Provisioning. When you are finished editing the list, click OK. Verify the list of administrators in the configuration dialog box. When the list is complete, click Next. 18.Use the Database Engine Configuration - Data Directories page to specify nondefault installation directories. To install to default directories, click Next. Important If you specify nondefault installation directories, ensure that the installation folders are unique to this instance of SQL Server. None of the directories in this dialog box should be shared with directories from other instances of SQL Server.

For more information, see Database Engine Configuration - Data Directories. 19.Use the Database Engine Configuration - FILESTREAM page to enable FILESTREAM for your instance of SQL Server. For more information, see Database Engine Configuration Filestream. 20.Use the Analysis Services Configuration — Account Provisioning page to specify users or accounts that will have administrator permissions for Analysis Services. You must specify at least one system administrator for Analysis Services. To add the account under which SQL Server Setup is running, click Add Current User. To add or remove accounts from the list of system administrators, click Add or Remove, and then edit the list of users, groups, or computers that will have administrator privileges for Analysis Services. For more information, see Analysis Services Configuration - Account Provisioning. When you are finished editing the list, click OK. Verify the list of administrators in the configuration dialog box. When the list is complete, click Next. 21.Use the Analysis Services Configuration — Data Directories page to specify nondefault installation directories. To install to default directories, click Next. Important If you specify nondefault installation directories, ensure that the installation folders are unique to this instance of SQL Server. None of the directories in this dialog box should be shared with directories from other instances of SQL Server. For more information, see Analysis Services Configuration - Data Directories. 22.Use the Reporting Services Configuration page to specify the kind of Reporting Services installation to create. Options include the following: • Native mode default configuration • SharePoint mode default configuration • Unconfigured Reporting Services installation For more information about Reporting Services configuration modes, see Report Server Installation Options. 23.On the Error Reporting page, specify the information that you want to send to Microsoft to help improve SQL Server. By default, option for error reporting is enabled. For more information, see Error Reporting. 24.The System Configuration Checker will run one more set of rules to validate your computer configuration with the SQL Server features that you have specified. 25.The Ready to Install page shows a tree view of installation options that were specified during Setup. To continue, click Install. 26.During installation, the Installation Progress page provides status so that you can monitor installation progress as Setup continues. 27.After installation, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the SQL Server installation process, click Close. 28.If you are instructed to restart the computer, do so now. It is important to read the message from the Installation Wizard when you have finished with Setup. For more information, see How to:

View and Read SQL Server Setup Log Files. Next Steps Configure your new SQL Server installation • To reduce the attackable surface area of a system, SQL Server selectively installs and enables key services and features. For more information, see Understanding Surface Area Configuration on MSDN. • For more information about how to use graphical tools and command prompt utilities, see Configuring SQL Server 2008 R2. See Also Other Resources How to: View and Read SQL Server Setup Log Files How to: Upgrade to SQL Server 2008 R2 (Setup) How to: Install SQL Server 2008 R2 from the Command Prompt Tags : Add a tag Add Cancel Flag as ContentBug Community Content Add new content

Annotations

Opening SQL Ports on Server's Firewall by command line script
Please Wait

MrMMills1 ... Internetero | Edit | Show History

Update firewall on Windows Server 2008 / Server 2008 R2 @echo off echo. *** OPENING SQL SERVER PORTS IN THE FIREWALL *** echo. source "http://rperreaux.spaces.live.com/Blog/cns!5D7BD18D324CBEEF!729.entry? wa=wsignin1.0&sa=289774293" echo. echo. Note for Named Instances - SQL mirroring - Dynamic Ports and the firewall echo. see http://msdn.microsoft.com/en-us/library/cc646023(v=SQL.100).aspx#BKMK_programs echo. You will need to open firewall ports for your mirroring endpoints and possibly dynamic ports echo. echo.

echo. Opening SQL Server TCP 1433 netsh advfirewall firewall add rule name="SQL Server (TCP 1432)" dir=in action=allow protocol=TCP localport=1433 profile=domain echo. echo. Opening SQL Admin Connection TCP 1434 netsh advfirewall firewall add rule name="SQL Admin Connection (TCP 1434)" dir=in action=allow protocol=TCP localport=1434 profile=domain echo. echo. Opening SQL Service Broker TCP 4022 netsh advfirewall firewall add rule name="SQL Service Broker (TCP 4022)" dir=in action=allow protocol=TCP localport=4022 profile=domain echo. echo. Port 135 netsh advfirewall firewall add rule name="SQL Debugger/RPC (TCP 135)" dir=in action=allow protocol=TCP localport=135 profile=domain echo. echo. Opening SQL Browser UDP 1434 netsh advfirewall firewall add rule name="SQL Browser (UDP 1434)" dir=in action=allow protocol=UDP localport=1434 profile=domain echo. echo. Opening Analysis Services TCP 2383 netsh advfirewall firewall add rule name="Analysis Services (TCP 2383)" dir=in action=allow protocol=TCP localport=2383 profile=domain echo. echo. Opening SQL Browser TCP 2382 netsh advfirewall firewall add rule name="SQL Browser (TCP 2382)" dir=in action=allow protocol=TCP localport=2382 profile=domain echo. echo. ***Done *** ***If your copying the script above be sure to put "profile=domain" on the same line, as the netsh command, above it. This post it wrapped it to the next line, when in reality it is on the same line. Additional Firewall Rules http://msdn.microsoft.com/enus/library/cc646023(v=SQL.100).aspx#BKMK_dynamic_ports The following procedure uses the Windows Firewall item in Control Panel. The Windows Firewall with Advanced Security MMC snap-in can configure a more complex rule. This includes configuring a service exception which can be useful for providing defense in depth. See Using the Windows Firewall with Advanced Security Snap-in below. To add a program exception to the firewall using the Windows Firewall item in Control Panel. On the Exceptions tab of the Windows Firewall item in Control Panel, click Add a program. Browse to the location of the instance of SQL Server that you want to allow through the firewall, for example C:\Program Files\Microsoft SQL Server\MSSQL10.<instance_name>\MSSQL\Binn, select sqlservr.exe, and then click Open. Click OK.

Tags : firewall (x) ports (x) sql (x) x64 (x) Add a tag Add Cancel Flag as ContentBug Install SQL 2008 x64 to different volume than C:\
Please Wait

MrMMills1 | Edit | Show History

echo. When you try to install SQL 2008 x64 on a new server it will echo. attempt to install the support files on the C volume by default echo. If you use a volume other than c: it won't complete because the WOW directory is not configured echo. echo. you can see lots of people with this error at echo. "http://www.google.com/search?q=setup.exe+%2FINSTALLSHAREDWOWDIR%3D++ %2FINSTALLSHAREDDIR%3D&sourceid=ie7&rls=com.microsoft:en-us:IE-SearchBox&ie=&oe=" echo. echo. Solution is to create the WOW directory, and use a command line to initiate the install echo. Be sure to change the install path in the GUI in the setup screen too. echo. This gets more of your SQL install to a volume other than C:\ but some files will still be installed on C:\ echo. echo. This script is about to create the following directory (swap out E for your drive letter) echo. "E:\Program Files (x86)\Microsoft SQL Server" md "E:\Program Files (x86)" md "E:\Program Files (x86)\Microsoft SQL Server" echo. setup.exe /INSTALLSHAREDWOWDIR="E:\Program Files (x86)\Microsoft SQL Server" /INSTALLSHAREDDIR="E:\Program Files\Microsoft SQL Server" /ACTION=install pause Good luck

Tags : Add a tag Add Cancel Flag as ContentBug

Please Wait

Hi there, If you experience logon problems to the Database Engine from SQL Server Management Studio after installation, try to start the SQL Server Management Studio with the "Run as Administrator" (rightclick) option. In my case, this resolved a 18456 error and allowed me to connect to the Database Engine.

Running SQL Server 2008 R2 on Windows Server 2008 R2. Regards, Marco

Tags : 18456; (x) 2008 (x) r2; (x) server (x) sql (x) Add a tag Add Cancel Flag as ContentBug How to install SQL Server 2008 R2 Alberto Morillo | Edit | Show History

Please Wait

Hello, If you would like to see a step-by-step guide on how to install SQL Server 2008 R2, please visit the following link: http://www.sqlcoffee.com/SQLServer2008_0013.htm Regards, Alberto Morillo SQLCoffee.com

Tags : Add a tag Add Cancel Flag as ContentBug | Edit

Tags : Add a tag Add Cancel Flag as ContentBug

© 2010 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statem