The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
To install Microsoft SQL Server, complete the following tasks:
Install and configure Microsoft SQL Server. For the most up-to-date details about any specific service pack or other requirements, see the Compatibility Matrix for Unified CCE at http://docwiki.cisco.com/wiki/Compatibility_Matrix_for_Unified_CCE.
Verify the SQL protocol order.
Install Microsoft SQL Server 2008 R2. Store the SQL Server log and temporary files on the same physical disk as the operating system (typically the C drive). Store the Logger database on the secondary drive (typically the E drive).
![]() Note | For information about supported versions, editions, and service packs, see the Compatibility Matrix for Unified CCE at http://docwiki.cisco.com/wiki/Compatibility_Matrix_for_Unified_CCE. |
![]() Note | The SQL Server 2008 R2 installation disables the Windows' Computer Browser service. The ICMDBA requires that service to run some of its functionality. If you need to run ICMDBA on this server, enable the Computer Browser service. |
Assign the Perform Volume Maintenance Tasks privilege by using the Microsoft Local Security Policy Tool from an administrator account. This privilege determines which users and groups can run maintenance tasks on a volume. (Refer to Microsoft documentation for more details.) When you finish the CCE installation or upgrade, remove the Perform Volume Maintenance Tasks privilege.
Any users who are involved in installing or upgrading a Unified ICM/CCE & Hosted solution must be added as part of SQL Server Security login and associated with the System Administrator role. Complete the following steps to set a user as a System Administrator:
Step 1 | Open the Microsoft SQL Server Management Studio using the System Administrator login credentials. | ||
Step 2 | In the Object
Explorer pane, click the
Security folder.
The Security folder expands. | ||
Step 3 | Right-click
the
Logins folder, and then click
New
Login.
The Login-New view appears. | ||
Step 4 | In the Login name field, enter the Windows login name of the user whom you want to associate with the System Administrator role. | ||
Step 5 | Click OK. | ||
Step 6 | In the Object
Explorer pane, click the
Server
Roles folder.
The Server Roles view appears. | ||
Step 7 | Check the
sysadmin check box.
System administrator is a predefined fixed server-level role in the Microsoft SQL Server. The system administrator performs operations on a site-level. System administrators manage jobs, role definitions, and shared schedules that are used to run reports. You must be a system administrator to create, modify, and delete individual records in the Configuration Manager tool. For details about the sysadmin role, see the Microsoft SQL documentation. | ||
Step 8 | Click
OK.
The user is now a part of the SQL Security login and is also associated with the System Administrator role. |
Step 1 | Click Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Server Configuration Manager. |
Step 2 | In the left pane, navigate to SQL Native Client 10.0 Configuration (32bit) > Client Protocols. |
Step 3 | In the right pane, right-click Named Pipes and select Order. |
Step 4 | In the Client Protocols Properties window, select Named Pipes and click the up arrow to move Named Pipes above TCP/IP, and then click OK. |
Step 5 | In the left pane, navigate to SQL Native Client 10.0 Configuration > Client Protocols. |
Step 6 | In the right pane, right-click Named Pipes and select Order. |
Step 7 | In the Client Protocols Properties window, select Named Pipes and click the up arrow to move Named Pipes above TCP/IP, and then click OK. |
Step 8 | In the left pane, navigate to SQL Server Network Configuration > Protocols for MSSQLSERVER. |
Step 9 | In the right pane, right-click Named Pipes and select Enable from the list. |
Use the Microsoft SQL Server Management Studio to increase the database, and log sizes.
For the Tempdb, follow these guidelines: