Bugs that are fixed in SQL Server 2012 Service Pack 2

• Email
• Print

Introduction

This article lists the bugs that are fixed in Microsoft SQL Server 2012 Service Pack 2 (SP2).

Notes

• Additional fixes that are not documented here may also be included in the service pack.
• This list will be updated when more articles are released.

For more information about how to obtain SQL Server 2012 service packs, click the following article number to view the article in the Microsoft Knowledge Base:

2755533 How to obtain the latest service pack for SQL Server 2012

Note For more information about which download you should select from the available downloads list, check the release notes here.

More information

SQL Server 2012 service packs are cumulative updates and upgrade all editions and service levels of SQL Server 2012 to SP2. In addition to the fixes that are listed in this article, this service pack contains up to and including Microsoft SQL Server 2012 SP1 Cumulative Update 9 (CU9). 

For more information about the cumulative update packages that are available for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Issues that are fixed in this service pack

For more information about the bugs that are fixed in SQL Server 2012 SP2, click the following article numbers to view the articles in the Microsoft Knowledge Base.

VSTS bug number	KB article number	Description
1374617	2028830	FIX: Shared components are installed in the wrong location when you implement a SQL Server 2008 or SQL Server 2012 Failover Cluster installation
1703014	2963382	FIX: Can't connect to the server when you run a cube creation MDX query in SSAS 2012
2011247	2927741	FIX: Image is not displayed correctly in the webpage when you use DrillThrough action on an SSRS 2012 report
2034994	2963383	FIX: Text truncated when you use HPB renderer to view a report in SSRS 2012
1769469	2963384	FIX: SQL Server crashes when the log file of tempdb database is full in SQL Server 2012
1973168	2963386	FIX: SSRS 2012 fails with IsolatedStorageException when subscriptions exported to Excel worksheets are larger than 10 MB
1973196	2963388	FIX: SSRS 2012 cannot export a report that is larger than 10 MB to Excel format
787358	2963404	FIX: Rollback causes database to go to suspect mode in SQL Server 2012
1043717	2806979	FIX: Poor performance when you run a query against a table in an RCSI-enabled database in SQL Server 2012
1178585	2963412	New DMF sys.dm_fts_index_keywords_position_by_document in SQL Server 2012 SP2
1182241	2966520	FIX: New log files are not created when you restart the Reporting Services Windows Service in SSRS 2012 on January 1
1240848	2966519	FIX: No error message when log backup failed in SQL Server 2012
1253861	2936004	FIX: Visual Studio 2012 crashes because of access violation when the data source binding is completed in Report Viewer 2012 UI in local mode
1262029	2966522	FIX: File Share subscription doesn't populate the description column in SSRS 2012
1481773	2966523	FIX: The "Name" drop-down list is empty when an SSRS 2012 report is specified
1419367	2964762	FIX: Event ID 22 or error 0xC1000016 will be logged when you use Discover command in SSAS 2012
2103903	2972285	FIX: Performance issues when you use SSISDB as your deployment store in SQL Server 2012
2021581	2965035	SSAS 2012 logging feature improvement in SQL Server 2012 Service Pack 2
203749	2952444	FIX: Poor performance when you use table variables in SQL Server 2012
2095064	2936328	FIX: Access violation occurs when you run CHECKTABLE or CHECKDB against a table that has persisted computed columns in SQL Server 2008 R2 or SQL Server 2012
1222472	2827857	FIX: DTA does not work on SQL Server 2012 instance that uses a supplementary character collation
2124209	2939277	FIX: Incorrect results when you run queries that contain UNION operator by using parallel query plan in SQL Server

Resolutions to the following issues are also included in SQL Server 2012 SP2.

VSTS bug number	Description
950185	Improved messaging around processing errors and warnings when you work with large HTML reports.
950189	Improved messaging around processing errors and warnings when you work with reports with large number of parameters.
994470	Incorrect results when you work with block mode unary operators.
1041277	DPM’s full backup on the server with AlwaysOn secondary will be converted to copy_only backup.
1278767	The value of tabular instance perfmon counters: Memory\VertiPaq <TypeName> KB is always 0.
1355346	The end SCOPE statement does not match the opening SCOPE statement.
1374617	FIX: Shared components are installed in the wrong location when you implement a SQL Server 2008 Failover Cluster installation
1610447	Uninitialized object leads to crashes and potentially wrong results when executing DAX expressions with conditional calculations.
1610492	A simple DAX query returns unexpected results when you use PowerPivot v2 11.0.3000.0.
2060218	"ACTIONABLE_HEAP_CORRUPTION" when SSRS configuration file is parsed by using an invalid InstanceId.
2065570	NonYieldProcessTable record in RING_BUFFER_NONYIELD_PROCESSTABLE ring buffer does not have user and kernel process time.
2075161	Provides platform information in the log of SSRS 2012
1347204	FIX: Access Violation when you insert data into a table that has a column with a sequence default from a cross-database transaction in SQL Server 2012
1184332	If a tail log backup is performed against the model database, model database will freeze in restoring state during a server restart that will prevent the SQL Server from starting successfully. This is because Tempdb database could not be created during the server startup and you receive the following error message: “Database '<DatabaseName>' cannot be opened"
1243853	Error 3456 occurs when restoring the log backup of a bulk-logged DB where a new data file was added with an initial size greater than 64704KB.
1404999	When you drop of a database snapshot is issued in a session with a LOCK_TIMEOUT setting, a time-out error may occur followed by an assertion error.
1190211	Installation of SQL Server by using InstallShield ends up in a hang state. For more information, go to this Knowledge Base article.
1386073	After you install SQL Server 2012 SP2, when SQL Server is stopped from either configuration manager or service control manager, an informational message is logged to the SQL Server immediately after shutdown is issued. In earlier versions, we issued this messages after internal services, such as the .NET Framework, service broker, were stopped.

Fixes for Connect Items submitted by the community

Connect Bug ID	Description
714689	Evaluation results are written to output xml file multiple times when you implement Enterprise Management Framework against multiple servers and an error occurs against one of the servers in the list.
735543	Database goes into a restore mode when its backup is restored as a different database on the same instance.
736509	You cannot debug a stored procedure that calls sp_executesql in SQL Server Management Studio (SSMS). When F11 is pressed, you receive an 'Object reference not set to an instance of object' error message.
740181	SSMS does not fully manage Full-Text in SQL Server Express.
745566	SQL Server SMO ignores default constraint in SQL Server 2012 and SQL Server 2014.
764197	SSMS handles Numbered Stored procedures inconsistently.
769121	"Column '<column name>' does not belong to table summary. (System.Data)" error message when replicating tables have the same names but are located in different schemas.
773710	After reverting to a database snapshot that contains full-text indexes, you cannot create any ft_catalogs until you either restart SQL Server, detach and then attach the database, or take the database offline and then set the database online.
774317	SSMS occasionally crashes on close, which then causes it to automatically restart
785064	"Value of 'null' is not valid for 'stream' " error message when you work with customer pipeline components in Business Intelligence Development Studio (BIDS).
785151	When you execute queries with Show Actual Query Plan turned on, the result of Null is returned, and you receive the following error message: Error: Msg 50000, Level 16, State 10, Procedure test, Line 34 String or binary data would be truncated.
791929	"A system assertion check has failed" error message when you insert data into a partitioned view that has triggers.
797967	Create script duplicates the statements when scripting column level permissions in SSMS.
799430	SSMS may crash when you try to refresh the SSMS window icon on the task bar.
804901	Deploying new versions of large projects encounters a time-out during deployment into SSIS Catalog database (SSISDB). Additionally, you receive the following error messages: Failed to deploy project. For more information, query the operation_messages view for the operation identifier ’219′. (Microsoft SQL Server, Error: 27203) Failed to deploy the project. Fix the problems and try again later.:Timeout expired. The timeout period

Create a New SQL Server Failover Cluster (Setup)

SQL Server 2016

Other Versions

 

Applies To: SQL Server 2016 Preview

To install or upgrade a SQL Server failover cluster, you must run the Setup program on each node of the failover cluster. To add a node to an existing SQL Server failover cluster, you must run SQL Server Setup on the node that is to be added to the SQL Server failover cluster instance. Do not run Setup on the active node to manage the other nodes.

Depending on how the nodes are clustered, the SQL Server failover cluster is configured in the following ways:

• Nodes on the same subnet or the same set of subnets - The IP address resource dependency is set to AND for these types of configurations.
• Nodes on different subnets - The IP address resource dependency is set to OR and this configuration is called a SQL Server multi-subnet failover cluster configuration. For more information, see SQL Server Multi-Subnet Clustering (SQL Server).

The following options are available for SQL Server failover cluster installation:

Option1: Integration Installation with Add Node

SQL Server integrated failover cluster installation consists of the following steps:

• Create and configure a single-node SQL Server failover cluster instance. When you configure the node successfully, you have a fully functional failover cluster instance. At this point, it does not have high availability because there is only one node in the failover cluster.
• On each node to be added to the SQL Server failover cluster, run Setup with Add Node functionality to add that node.
  • If the node you are adding has additional or different subnets, Setup allows you to specify additional IP addresses. If the node you are adding is on a different subnet, you also need to confirm the IP address resource dependency change to OR. For more information on the different possible scenarios during Add Node operations, see Add or Remove Nodes in a SQL Server Failover Cluster (Setup).

Option 2: Advanced/Enterprise Installation

SQL Server Advanced/Enterprise failover cluster installation consists of the following steps:

• On each node that is a possible owner of the new SQL Server failover cluster, follow the Prepare Failover Cluster setup steps that are listed in thePrepare section. After you run the Prepare Failover Cluster on one node, Setup creates the Configuration.ini file that lists all the settings that you specified. On the additional nodes to be prepared, instead of following these steps, you can supply the autogenerated Configuration.ini file from first node as an input to the Setup command line. For more information, see Install SQL Server 2016 Using a Configuration File. This step prepares the nodes ready to be clustered, but there is no operational instance of SQL Server at the end of this step.
• After the nodes are prepared for clustering, run Setup on one of the prepared nodes. This step configures and finishes the failover cluster instance. At the end of this step, you will have an operational SQL Server failover cluster instance and all the nodes that were prepared previously for that instance will be the possible owners of the newly-created SQL Server failover cluster.
  If you are clustering nodes on multiple subnets, Setup will detect the union of all the subnets across all nodes that have the SQL Server prepared failover cluster instance. You will be able to specify multiple IP addresses for the subnets. Each prepared node must be the possible owner of at least one IP address.
  If each of the IP addresses specified for the subnets are supported on all the prepared nodes, the dependency is set to AND.
  If each of the IP addresses specified for the subnets are not supported on all the prepared nodes, the dependency is set to OR. For more information, see SQL Server Multi-Subnet Clustering (SQL Server).

  Note
  Complete Failover Cluster requires that the underlying Windows failover cluster exists. If the Windows failover cluster does not exist, Setup gives an error and exits.

For more information about how to add nodes to or remove nodes from an existing failover cluster instance, see Add or Remove Nodes in a SQL Server Failover Cluster (Setup).

For more information about remote installation, see Supported Version and Edition Upgrades.

For more information about installing Analysis Services in a Windows failover cluster, see How to Cluster SQL Server Analysis Services.

Prerequisites

Before you begin, review the following SQL Server Books Online topics:

• Planning a SQL Server Installation
• Before Installing Failover Clustering
• Security Considerations for a SQL Server Installation
• SQL Server Multi-Subnet Clustering (SQL Server)

Note
Take note of the location of the shared drive in the Cluster Administrator before you run SQL Server Setup. You must have this information to create a new failover cluster.

To install a new SQL Server failover cluster using Integrated Install with Add Node.

1. Insert the SQL Server installation media, and from the root folder, double-click Setup.exe. To install from a network share, browse to the root folder on the share, and then double-click Setup.exe. For more information about how to install prerequisites, see Before Installing Failover Clustering.
2. The Installation Wizard starts the SQL Server Installation Center. To create a new cluster installation of SQL Server, click New SQL Server failover cluster installation on the installation page.
3. The System Configuration Checker runs a discovery operation on your computer. To continue, Click OK. . You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.
4. To continue, click Next.
5. On the Setup Support Files page, click Install to install the Setup support files.
6. The System Configuration Checker verifies the system state of your computer before Setup continues. After the check is complete, click Next to continue. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.
7. On the Product key page, indicate whether you are installing a free edition of SQL Server, or whether you have a PID key for a production version of the product. For more information, see Editions and Components of SQL Server 2016.
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. Click Next to continue. To end Setup, clickCancel.
9. 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, but only Database Engine, Analysis Services in tabular mode, and Analysis Services in multidimensional mode support failover clustering. Other selected components will run as a stand-alone feature without failover capability on the current node that you are running Setup on. For more information on Analysis Services modes, see Determine the Server Mode of an Analysis Services Instance.

   The prerequisites for the selected features are displayed on the right-hand pane. SQL Server Setup will install the prerequisite that are not already installed during the installation step described later in this procedure.

   You can specify a custom directory for shared components by using the field at the bottom of this page. To change the installation path for shared components, either update the path in the field provided at the bottom of the dialog box, or click the ellipsis button to browse to an installation directory. The default installation path is C:\Program Files\Microsoft SQL Server \.

   SQL Server also supports installing system databases (Master, Model, MSDB, and TempDB), and Database Engine user databases on a Server Message Block (SMB) file share. For more information on installing SQL Server with SMB file share as a storage, see Install SQL Server with SMB Fileshare as a Storage Option.

   The path specified for the shared components must be an absolute path. The folder must not be compressed or encrypted. Mapped drives are not supported. If you are installing SQL Server on a 64-bit operating system, you will see the following options:

   1. Shared feature directory
   2. Shared feature directory (x86)

   The path specified for each of the above options must be different.

   Note
   When you select the Database Engine Services feature, both replication and full-text search are selected automatically. Data Quality Services (DQS) is also selected when you select the Database Engine Services feature. Unselecting any of these subfeatures also unselects the Database Engine Services feature.

10. SQL Server setup runs one more set of rules that are based on the features you selected to validate your configuration.
11. On the Instance Configuration page, specify whether to install a default or a named instance. For more information, see Instance Configuration.

    SQL Server Network Name — Specify a network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.

    Note
    This is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters.

    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 box and provide a value.

    Note
    Typical stand-alone instances of SQL Server, whether default or named instances, do not use a nondefault value for the Instance ID box.

    Instance root directory — By default, the instance root directory is C:\Program Files\Microsoft SQL Server\. To specify a nondefault root directory, use the field provided, or click the ellipsis button to locate an installation folder.

    Detected SQL Server instances and features on this computer - 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. Click Next to continue.
12. Use the Cluster Resource Group page to specify the cluster resource group name where SQL Server virtual server resources will be located. To specify the SQL Server cluster resource group name, you have two options:

    • Use the drop-down box to specify an existing group to use.
    • Type the name of a new group to create. Be aware that the name "Available storage" is not a valid group name.
13. On the Cluster Disk Selection page, select the shared cluster disk resource for your SQL Server failover cluster. The cluster disk is where the SQL Server data will be put. More than one disk can be specified. The Available shared disks grid displays a list of available disks, whether each is qualified as a shared disk, and a description of each disk resource. Click Next to continue.

    Note
    The first drive is used as the default drive for all databases, but can be changed on the Database Engine or Analysis Services configuration pages. On the Cluster Disk Selection page, you can optionally skip selecting any shared disk if you want to use SMB fileshare as a data folder.

14. On the Cluster Network Configuration page, specify the network resources for your failover cluster instance:

    • Network Settings — Specify the IP type and IP address for your failover cluster instance.

    Click Next to continue.
15. Use this page to specify Cluster Security Policy.

    • Windows Server 2008 and later versions - Service SIDs (server security IDs) are the recommended and default setting. There is no option for changing this to security groups. For information about service SIDs functionality on Windows Server 2008, see Configure Windows Service Accounts and Permissions. This has been tested in standalone and cluster setup on Windows Server 2008 R2.
    • On Windows Server 2003, specify domain groups for SQL Server services. All resource permissions are controlled by domain-level groups that include SQL Server service accounts as group members.

    Click Next to continue.
16. 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 (Database Engine, Analysis Services, and Reporting Services).
17. 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. The startup type is set to manual for all cluster-aware services, including full-text search and SQL Server Agent, and cannot be changed during installation. 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 complete their tasks. For more information, see Server Configuration - Service Accounts andConfigure Windows Service Accounts and Permissions.

    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.
18. Use the Server Configuration - Collation tab to specify nondefault collations for the Database Engine and Analysis Services. For more information, see Server Configuration - Collation.
19. 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 Addor 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, clickNext.
20. Use the Database Engine Configuration - Data Directories page to specify nondefault installation directories. To install to default directories, clickNext.

    Important
    If you specify nondefault installation directories, make sure 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. The data directories should be located on the shared cluster disk for the failover cluster.

    Note
    To specify a Server Message Block (SMB) file server as the Data Directory, set default data root directory to the fileshare of the format \\Servername\ShareName\...

    For more information, see Database Engine Configuration - Data Directories.
21. Use the Database Engine Configuration - FILESTREAM page to enable FILESTREAM for your instance of SQL Server. For more information about FILESTREAM, see Database Engine Configuration - Filestream. Click Next to continue.
22. 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, clickNext.
23. 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, make sure 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. The data directories should be located on the shared cluster disk for the failover cluster.

    For more information, see Analysis Services Configuration - Data Directories.
24. Use the Reporting Services Configuration page to specify the kind of Reporting Services installation to create. For failover cluster installation, the option is set to Unconfigured Reporting Services installation. You must configure Reporting Services services after you complete the installation.

    For more information about Reporting Services configuration modes, see Reporting Services Configuration Options (SSRS).
25. The System Configuration Checker runs one more set of rules to validate your configuration with the SQL Server features that you have specified.
26. The Ready to Install page displays a tree view of installation options that were specified during Setup. To continue, click Install. Setup will first install the required prerequisites for the selected features followed by the feature installation.
27. During installation, the Installation Progress page provides status so that you can monitor installation progress as Setup continues.
28. 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.
29. 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 information about Setup log files, see View and Read SQL Server Setup Log Files.
30. To add nodes to the single-node failover you just created, run Setup on each additional node and follow the steps for AddNode operation. For more information, see Add or Remove Nodes in a SQL Server Failover Cluster (Setup).

    Note

    If you are adding more than one node, you can use the configuration file to deploy the installations. For more information, see Install SQL Server 2016 Using a Configuration File. The SQL Server edition you are installing must match across all the nodes in a SQL Server failover cluster. When you add a new node to an existing SQL Server failover cluster, make sure that you specify that the edition matches the edition of the existing failover cluster.

Prepare

Advanced/Enterprise Failover Cluster Install Step 1: Prepare

1. Insert the SQL Server installation media, and from the root folder, double-click Setup.exe. To install from a network share, browse to the root folder on the share, and then double-click Setup.exe. For more information about how to install prerequisites, see Before Installing Failover Clustering. You may be asked to install the prerequisites, if they are not previously installed.
2. Windows Installer 4.5 is required, and may be installed by the Installation Wizard. If you are prompted to restart your computer, restart and then start SQL Server Setup again.
3. After the prerequisites are installed, the Installation Wizard starts the SQL Server Installation Center. To prepare the node for clustering, move to the Advanced page and then click Advanced cluster preparation.
4. The System Configuration Checker runs a discovery operation on your computer. To continue, Click OK. . You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.
5. On the Setup Support Files page click Install to install the Setup support files.
6. The System Configuration Checker verifies the system state of your computer before Setup continues. After the check is complete, click Nextto continue. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.
7. 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.
8. On the Product key page, click to indicate whether you are installing a free edition of SQL Server, or whether you have a PID key for a production version of the product. For more information, see Editions and Components of SQL Server 2016.

   Note
   You must specify the same product key on all the nodes that you are preparing for the same failover cluster.

9. 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. Click Next to continue. To end Setup, clickCancel.
10. 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, but only Database Engine, Analysis Services in tabular mode, and Analysis Services in multidimensional mode support failover clustering. Other selected components will run as a stand-alone feature without failover capability on the current node that you are running Setup on. For more information on Analysis Services modes, seeDetermine the Server Mode of an Analysis Services Instance.

    The prerequisites for the selected features are displayed on the right-hand pane. SQL Server Setup will install the prerequisite that are not already installed during the installation step described later in this procedure.

    You can specify a custom directory for shared components by using the field at the bottom of this page. To change the installation path for shared components, either update the path in the field provided at the bottom of the dialog box, or click the ellipsis button to browse to an installation directory. The default installation path is C:\Program Files\Microsoft SQL Server\.

    Note
    When you select the Database Engine Services feature, both replication and full-text search are selected automatically. Unselecting any of these subfeatures also unselects the Database Engine Services feature.

11. On the Instance Configuration page, specify whether to install a default or a named instance. For more information, see Instance Configuration.

    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 text box and provide a value.

    Note
    Typical stand-alone instances of SQL Server, whether default or named instances, do not use a nondefault value for the Instance ID text box.

    Important
    Use the same InstanceID for all the nodes that are prepared for the failover cluster

    Instance root directory — By default, the instance root directory is C:\Program Files\Microsoft SQL Server\. To specify a nondefault root directory, use the field provided, or click the ellipsis button to locate an installation folder.

    Installed instances - 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. Click Next to continue.
12. The Disk Space Requirements page calculates the required disk space for the features that you specify, and compares requirements to the available disk space on the computer where Setup is running.
13. Use this page to specify Cluster Security Policy.

    • Windows Server 2008 and later versions - Service SIDs (server security IDs) are the recommended and default setting. There is no option for changing this to security groups. For information about service SIDs functionality on Windows Server 2008, see Configure Windows Service Accounts and Permissions. This has been tested in standalone and cluster setup on Windows Server 2008 R2.
    • On Windows Server 2003, specify domain groups for SQL Server services. All resource permissions are controlled by domain-level groups that include SQL Server service accounts as group members.

    Click Next to continue.
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. The startup type is set to manual for all cluster-aware services, including full-text search and SQL Server Agent, and cannot be changed during installation. 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 complete their tasks. For more information, see Server Configuration - Service Accounts and Configure Windows Service Accounts and Permissions.

    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 Server Configuration - Filestream to enable FILESTREAM for your instance of SQL Server. For more information, see Database Engine Configuration - Filestream. Click Next to continue.
18. Use the Reporting Services Configuration page to specify the kind of Reporting Services installation to create. For failover cluster installation, the option is set to Unconfigured Reporting Services installation. You must configure Reporting Services services after you complete the installation.

    For more information about Reporting Services configuration modes, see Reporting Services Configuration Options (SSRS).
19. On the Error Reporting page, specify the information that you want to send to Microsoft that will help improve SQL Server. By default, options for error reporting is enabled.
20. The System Configuration Checker runs one more set of rules to validate your configuration with the SQL Server features that you have specified.
21. The Ready to Install page displays a tree view of installation options that were specified during Setup. To continue, click Install. Setup will first install the required prerequisites for the selected features followed by the feature installation.

    During installation, the Installation Progress page provides status so that you can monitor installation progress as Setup continues. After installation, the Complete page provides a link to the summary log file for the installation and other important notes.
22. To complete the SQL Server installation process, click Close.
23. 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 information about Setup log files, see View and Read SQL Server Setup Log Files.
24. Repeat the previous steps to prepare the other nodes for the failover cluster. You can also use the autogenerated configuration file to run prepare on the other nodes. For more information, see Install SQL Server 2016 Using a Configuration File.

Complete

Advanced/Enterprise Failover Cluster Install Step 2: Complete

1. After preparing all the nodes as described in the prepare step, run Setup on one of the prepared nodes, preferably the one that owns the shared disk. On the Advanced page of the SQL Server Installation Center, click Advanced cluster completion.
2. The System Configuration Checker runs a discovery operation on your computer. To continue, Click OK. . You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.
3. On the Setup Support Files page, click Install to install the Setup support files.
4. The System Configuration Checker verifies the system state of your computer before Setup continues. After the check is complete, click Nextto continue. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.
5. 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.
6. Use the Cluster node configuration page to select the instance name prepared for clustering, and specify the network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.

   Note
   This is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters.

7. SQL Server setup runs one more set of rules that are based on the features you selected to validate your configuration.
8. Use the Cluster Resource Group page to specify the cluster resource group name where SQL Server virtual server resources will be located. To specify the SQL Server cluster resource group name. You have two options:

   • Use the list to specify an existing group to use.
   • Type the name of a new group to create. Be aware that the name "Available storage" is not a valid group name.
9. On the Cluster Disk Selection page, select the shared cluster disk resource for your SQL Server failover cluster. The cluster disk is where the SQL Server data will be put. More than one disk can be specified. The Available shared disks grid displays a list of available disks, whether each is qualified as a shared disk, and a description of each disk resource. Click Next to continue.

   Note
   The first drive is used as the default drive for all databases, but can be changed on the Database Engine or Analysis Services configuration pages.

10. On the Cluster Network Configuration page, specify the network resources for your failover cluster instance:

    • Network Settings — Specify the IP type and IP address for all the nodes and subnets for your failover cluster instance. You can specify multiple IP addresses for a multi-subnet failover cluster, but only one IP address per subnet is supported. Every prepared node should be an owner of at least one IP address. If you have multiple subnets in your SQL Server failover cluster, you will be prompted to set the IP address resource dependency to OR.

    Click Next to continue.
11. 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.
12. 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.
13. 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, make sure 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. The data directories should be located on the shared cluster disk for the failover cluster.

    For more information, see Database Engine Configuration - Data Directories.
14. 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.
15. 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, make sure 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. The data directories should be located on the shared cluster disk for the failover cluster.

    For more information, see Analysis Services Configuration - Data Directories.
16. The System Configuration Checker runs one more set of rules to validate your configuration with the SQL Server features that you have specified.
17. The Ready to Install page displays a tree view of installation options that were specified during Setup. To continue, click Install. Setup will first install the required prerequisites for the selected features followed by the feature installation.
18. During installation, the Installation Progress page provides status so that you can monitor installation progress as Setup continues.
19. 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. With this step, all the prepared nodes for the same failover cluster are now part of the completed SQL Server failover cluster.

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 Surface Area Configuration.

For more information about log file locations, see View and Read SQL Server Setup Log Files.

See Also