Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 01-Text | 8.40 MB |
|
|
Turning off the Windows firewall
Registering the SQL Server license
Installing the SQL Server client
Modifying the maximum server memory for the SQL Server
Starting the SQL Server Browser service
Changing the SQL Server service startup account
SQL Server 2014 in IMC
Before installing IMC, install the SQL Server on a database server used for storing IMC data, or install it on the server on which you plan to install IMC.
This document provides installation and configuration procedures for Microsoft SQL Server 2014. For more information about using the database for IMC, see the H3C IMC deployment guides.
If you plan to install the database on a separate database server, follow these guidelines:
· Before installing IMC, install a SQL Server client on the same server as IMC. The client version must match the version of the SQL Server the database.
· Before installing IMC, create a data file folder for storing IMC data on the database server. You must specify the local path to the folder during the deployment of IMC components, as shown in Figure 1.
Figure 1 Database Configuration dialog box during IMC installation
|
|
NOTE: Use Microsoft SQL Server licensed installation software. Localized software or other unauthorized editions might cause a failure in database installation and operation. |
Preparing for installation
Before installing SQL Server 2014 and the SQL Server client, configure the following settings:
· Install .Net Framework 3.5 (online or manually) on which SQL Server 2014 depends.
· Turn off the Windows firewall on the SQL Server host to open TCP port 1443.
Installing .Net Framework 3.5
The following procedure describes how to install .Net Framework 3.5 to Windows Server 2012 R2.
1. Copy the sources/sxs folder in the Windows Server 2012 R2 installation CD or ISO image to the root directory of a disk partition (for example, drive C), as shown in Figure 2.
Figure 2 Copying the sources/sxs folder
2. Run Windows PowerShell as the administrator by executing the following command:
Install-WindowsFeature –Name NET-Framework-Core –source c:\sources\sxs
Where, c:\sources\sxs is the path of the copied folder. Edit the path as needed.
Figure 3 shows the installation result.
Turning off the Windows firewall
1. Select Start > Control Panel > System and Security > Windows Firewall.
The Windows Firewall page opens, as shown in Figure 4.
Figure 4 Windows Firewall page
2. Select Turn Windows Firewall on or off.
The Customize Settings page opens, as shown in Figure 5.
Figure 5 Customize Settings page
3. Select Turn off Windows Firewall (not recommended) for both Private network settings and Public network settings, and then click OK.
The Windows Firewall page displays the firewall status.
Figure 6 Disabling Windows firewall
Installing SQL Server 2014
1. Run the installation program.
The SQL Server Installation Center wizard opens, as shown in Figure 7.
Figure 7 SQL Server Installation Center wizard
2. Select Installation in the navigation tree, and then select New SQL Server stand-alone installation or add features to an existing installation.
The Product Key page opens, as shown in Figure 8.
3. Enter the product key and then click Next.
The License Terms page opens, as shown in Figure 9.
4. Select I accept the license terms and click Next.
The Global Rules page opens, as shown in Figure 10.
When the check has been passed, the Microsoft Update page opens, as shown in Figure 11.
Figure 11 Microsoft Update page
5. Click Next.
The Product Updates page opens.
6. Click Next if no update is required.
The Install Setup Files page opens, as shown in Figure 12.
Figure 12 Install Setup Files page
When system preparations are complete, the Install Rules page opens, as shown in Figure 13.
When the rules check is complete, the Setup Role page opens, as shown in Figure 14.
7. Select SQL Server Feature Installation and click Next.
The Feature Selection page opens, as shown in Figure 15.
Figure 15 Feature Selection page
8. Select the features to install, and then specify directories in the Instance root directory, Shared feature directory, and Shared feature directory (x86) fields.
The default directory settings are C:\Program Files\Microsoft SQL Server, C:\Program Files\Microsoft SQL Server, and C:\Program Files(x86)\Microsoft SQL Server. Only the drive letter can be modified. You can specify another drive with sufficient space for the directories. This example uses disk drive D.
9. Click Next.
The Feature Rules page opens, as shown in Figure 16.
When the feature rules check is complete, the Instance Configuration page opens, as shown in Figure 17.
Figure 17 Instance Configuration page
10. Install a default instance or a named instance of the SQL Server.
¡ To install the default instance, select Default instance and specify an instance ID. The default instance ID is MSSQLSERVER.
¡ To install a name instance, select Named Instance and specify an instance ID. You are required to provide the instance name during IMC installation.
In this example, select Default instance and use the default instance ID MSSQLSERVER.
11. Click Next.
The Server Configuration page opens, as shown in Figure 18.
Figure 18 Server Configuration page
12. Use the default settings on the Service Accounts tab.
If you selected Named instance for the SQL Server in Figure 17, set Startup Type for the SQL Server Browser service to Automatic.
13. Click the Collation tab, as shown in Figure 19.
14. Use the default collation settings or modify the settings to meet specific language requirements, and then click Next.
The Database Engine Configuration page opens, as shown in Figure 20.
Figure 20 Database Engine Configuration page
15. Under Authentication Mode, select Mixed Mode, enter the password for user sa, and add a SQL Server administrator, as shown in Figure 21.
· SQL Server 2014 has password complexity requirements. For more information, see the SQL Server 2014 online help.
· For IMC to identify the sa logon password during installation, make sure the password does not contain any of the following characters:
¡ Left angle bracket (<)
¡ Right angle bracket (>)
¡ Vertical bar (|)
¡ Tab (\t)
· If the password of user sa must contain any of the previous characters, create a superuser with sa user privileges before the IMC installation. Make sure the password of the superuser does not contain any of the previous characters. For information about creating a database superuser, see "Creating a superuser."
Figure 21 Specifying SQL Server administrators
16. Use the default settings on the Data Directories tab, as shown in Figure 22.
Figure 22 Data Directories tab
17. Use the default settings on the FILESTREAM tab, as shown in Figure 23.
18. Click Next.
The Feature Configuration Rules page opens, as shown in Figure 24.
Figure 24 Feature Configuration Rules page
When the features check has been passed, the Ready to Install page opens, as shown in Figure 25.
Figure 25 Ready to Install page
19. Click Install.
The Installation Progress page opens, as shown in Figure 26.
Figure 26 Installation Progress page
When the installation is complete, the Complete page opens, as shown in Figure 27.
Figure 27 Complete page
20. Click Close.
Registering the SQL Server license
The SQL Server supports the following license registration modes:
· Per User licensing—Used to register the SQL Server 2012 Developer and Parallel Data Warehouse.
· Per Core licensing—Used to register the SQL Server 2012 and later versions. For a server installed with the SQL Server component, the number of core licenses is determined by the total number of cores on all processors. You must buy one core license for each core. If the number of cores is less than four on a processor, four core licenses are still required for the processor. With Per Core licensing, the number of SQL servers and IMC servers is not relevant. Per Core licensing is applicable to networks that contain several SQL servers and IMC servers. Figure 28 displays an example of Per Core licensing for SQL Server 2012.
· Server/CAL licensing—The number of Server/CAL licenses is determined by the number of SQL servers and IMC servers. You must buy a server license for each SQL server and a CAL license for each IMC server. Server/CAL licensing is applicable to networks that contain few SQL servers and IMC servers. Figure 29 displays an example of Server/CAL licensing for SQL Server 2008 R2.
Figure 29 Server/CAL licensing
Before choosing a license registration mode, determine the IMC deployment environment:
· If IMC is deployed in centralized mode, buy a CAL license for the IMC server only.
· If IMC is deployed in distributed mode, buy a CAL license for each IMC server that must access the SQL Server.
For more information about SQL Server license registration, see the related Microsoft documentation.
|
|
NOTE: The license registration modes apply to the Standard and Enterprise editions of SQL Server 2012/2014. You do not need to buy a license for other editions such as the Express edition. |
Installing the SQL Server client
Installation procedure
|
IMPORTANT: You must install the SQL Server client on all IMC servers (including subordinate servers). |
To install the SQL Server client:
1. Run the SQL Server 2014 installation program.
2. In the Feature Selection page, select the features as shown in Figure 30.
For information about displaying the Feature Selection page, see "Installing SQL Server 2014."
Figure 30 Feature Selection page
3. Click Next.
The Feature Rules page opens, as shown in Figure 31.
When the feature rules check is complete, the Server Configuration page opens, as shown in Figure 32.
Figure 32 Server Configuration page
4. Set the account name of SQL Server Integration Service to NT AUTHORITY\SYSTEM, and then click Next.
The Feature Configuration Rules page opens, as shown in Figure 33.
Figure 33 Feature Configuration Rules page
When the feature configuration rules check is complete, the Ready to Install page opens, as shown in Figure 34.
Figure 34 Ready to Install page
5. Click Install.
The Installation Progress page opens, as shown in Figure 35.
Figure 35 Installation Progress page
When the installation is complete, the Complete page opens, as shown in Figure 36.
Figure 36 Complete page
6. Click Close.
7. Restart the operating system.
Testing connectivity
To test the connectivity between the client and the SQL Server database:
1. Select Run from the Start menu, and then enter cmd in the Run dialog box.
2. In the CMD window, enter one of the following commands:
¡ For the default instance:
osql –S 192.168.20.110 –U sa –P iMC123456
¡ For a named instance:
osql –S 192.168.20.110\instancename –U sa –P iMC123456
In these commands, 192.168.20.110 is the IP address of the SQL Server database, sa and iMC123456 are the username and password of the default superuser, and instancename represents the named instance.
If the SQL command prompt is displayed, you have connected to the SQL Server database, as shown in Figure 37).
Figure 37 Testing connectivity
Configuring SQL Server 2014
The following information describes the procedures to configure the SQL Server database.
Configuring TCP/IP properties
1. Select Start > SQL Server 2014 Configuration Manager.
The SQL Server Configuration Manager opens.
2. From the navigation tree, select SQL Server Network Configuration > Protocols for MSSQLSERVER, as shown in Figure 38.
Figure 38 SQL Server Configuration Manager
3. Right-click TCP/IP and select Properties from the shortcut menu.
The TCP/IP Properties dialog box opens, as shown in Figure 39.
Figure 39 TCP/IP Properties dialog box
4. On the Protocol tab, make sure Yes is selected for Listen All.
5. Click the IP Addresses tab, select Yes for the Enabled option of each IP address, and set TCP Port to 1433, as shown in Figure 40.
6. Click OK.
The system displays a message that indicates the database service must be restarted to validate the configuration.
7. Click OK.
8. Restart the SQL Server service. For more information, see "Restarting the SQL Server service."
|
|
NOTE: · When Yes is selected for Listen All on the Protocol tab, the SQL Server automatically updates IP address settings after an IP address is changed. If you selected No, you must manually update the IP addresses. · You can enable the Named Pipes property in the same way. · In distributed deployment, make sure you configure all database servers to use the same listening port. |
Modifying the maximum server memory for the SQL Server
To ensure the optimum performance, the SQL Server is preemptive and uses a default maximum server memory of 2147483647 MB. When IMC and the SQL Server are installed on the same server, you must reduce the maximum server memory for the SQL Server. As a best practice, set the maximum server memory to half the server's physical memory.
To modify the maximum server memory for the SQL Server:
1. Select Start > SQL Server 2014 Management Studio.
2. In the Connect to Server dialog box, configure the following parameters, as shown in Figure 41:
a. Select SQL Server Authentication for the Authentication field.
b. Enter sa in the Login field.
c. Enter the password in the Password field.
Figure 41 Database login dialog box
3. Click Connect.
The Microsoft SQL Server Management Studio (Administrator) page opens, as shown in Figure 42.
Figure 42 Microsoft SQL Server Management Studio page
4. Right-click the server name and select Properties from the shortcut menu.
The Server Properties page opens.
5. Select Memory in the navigation tree, set the maximum server memory to half the server's physical memory, and click OK. This example uses 2048 MB.
Figure 43 Setting memory options for the SQL Server
6. Restart the operating system to validate the modification.
Starting the SQL Server Browser service
To enable IMC to connect to a named instance of SQL Server 2014, you must start the SQL Server Browser service after the SQL Server installation is complete.
If you set Startup Type for the SQL Server Browser service to Automatic during the SQL Server installation process, you do not need to start the SQL Server Browser service after the installation is complete.
To start the SQL Server Browser service:
1. Select Start > SQL Server 2014 Configuration Manager.
2. Select SQL Server Services from the navigation tree, right-click SQL Server Browser on the main pane, and then select Properties from the shortcut menu.
Figure 44 Launching the SQL Server Browser Properties dialog box
3. Click the Service tab and then select Automatic for Start Mode.
Figure 45 Setting the service start mode to Automatic
4. Click OK.
The dialog box closes.
5. Right-click SQL Server Browser, and then select Start from the shortcut menu.
Figure 46 Starting the SQL Server Browser service
Changing the SQL Server service startup account
When you specify a superuser for IMC to use a remote SQL Server database, that user must have write permissions to all the disks on the database server. To ensure these user capabilities, you must configure the SQL Server service to start up using the built-in local system account.
To configure the SQL Server service to start up using the built-in local system account:
1. Select Start > All Programs > Microsoft SQL Server 2014 > Configuration Tools > SQL Server Configuration Manager.
2. From the navigation tree, select SQL Server Services.
The main pane displays the services installed by SQL Server, as shown in Figure 47.
Figure 47 Services installed by SQL Server
3. Right-click SQL Server (MSSQLSERVER), and then select Properties from the shortcut menu.
4. Click the Log On tab.
Figure 48 Log On tab
5. Make sure Local System is selected for the Built-in account list.
6. Click OK.
7. Restart the SQL Server service to validate the configuration.
Restarting the SQL Server service
1. Select Start > All Programs > Microsoft SQL Server 2014 > Configuration Tools > SQL Server Configuration Manager.
2. From the navigation tree, select SQL Server Services.
3. Right-click SQL Server (MSSQLSERVER) on the main pane.
4. Click the Restart service icon 
on the
toolbar, as shown in Figure 49.
Figure 49 Restarting the SQL Server service
Creating a superuser
The SQL Server database has a default superuser named sa. To specify another user for database access during IMC installation, first create a login user and grant administrator privilege to the user on the SQL Server.
To create a superuser:
1. Select Start > SQL Server 2014 Management Studio.
The database login dialog box opens, as shown in Figure 50.
Figure 50 Login dialog box
2. Select SQL Server Authentication for Authentication, select a login username, enter the password, and then click Connect.
The Microsoft SQL Server Management Studio page opens, as shown in Figure 51.
Figure 51 Microsoft SQL Server Management Studio page
3. Expand the Security node in the navigation tree, right-click Logins, and select New Login from the shortcut menu.
The Login - New page opens, as shown in Figure 52.
4. On the General page, enter the login name, click SQL Server authentication, enter the password, and then clear User must change password at next login. This example uses imctest as the login name.
For IMC to correctly identify the password, make sure the password does not contain any of the following characters:
· Left angle racket (<)
· Right angle bracket (>)
· Vertical bar (|)
· Tab (\t)
5. From the navigation tree, select Server Roles.
Figure 53 Setting server roles
6. Select public and sysadmin and click OK.
The user is granted database administrator privileges and is displayed under the Security > Logins node in the navigation tree of Microsoft SQL Server Management Studio, as shown in Figure 54.
Figure 54 Viewing the new user
Uninstalling SQL Server 2014
1. Select Start > Control Panel > Uninstall or Change a program > Uninstall/Change.
2. Select Microsoft SQL Server 2014 (64-bit), and then click Uninstall.
3. Follow the same procedure to uninstall other programs shown in Figure 55.
Figure 55 Uninstalling SQL Server 2014
FAQ
The default instance of the database is used by another application. How do I install the database using a named instance?
The installation procedure for using a named instance is similar to the installation procedure for using the default instance. The following information describes only the differences.
1. After the Setup Support Rules check is complete, click Next.
The Installation Type page opens, as shown in Figure 56.
Figure 56 Installation Type page
2. Select Perform a new installation of SQL Server 2014 and then click Next.
3. Enter the product key, accept the license terms, and then select the setup role.
The Feature Selection page opens.
Figure 57 Feature Selection page
4. Select the features shown in Figure 57, and then click Next.
When the rule check is complete, the Instance Configuration page opens, as shown in Figure 58.
Figure 58 Instance Configuration page
5. Select Named instance, enter an instance name, and then click Next.
The Server Configuration page opens.
Figure 59 Server Configuration page
6. Configure the account names for the SQL Server services shown in Figure 59.
7. Click Next.
The Database Engine Configuration page opens, as shown in Figure 60.
Figure 60 Database Engine Configuration page
8. Under Authentication Mode, select Mixed Mode, and then enter the password of user sa. Make sure the password does not contain any of the following characters:
¡ Left angle bracket (<)
¡ Right angle bracket (>)
¡ Vertical bar (|)
¡ Tab (\t)
Use the default settings on the Data Directories and FILESTREAM tabs. The next setup steps are the same as those for the default instance.
Does changing the computer name affect the database? How do I restore the database?
Changing the name of the computer running the SQL Server might cause database operations to fail.
Perform the following steps to update the computer name saved in the database. In this example, the old computer name is SERVER_1, and the new computer name is SERVER_2.
1. Open the CMD window and execute the following scripts (the login username is sa, and the password is iMCpass):
osql -Usa -PiMCpass
select @@SERVERNAME
go
The old computer name SERVER_1 is displayed in the interface.
2. Execute the following commands to modify the computer name saved in the database:
sp_dropserver @server=‘SERVER_1’, @droplogins=NULL
go
sp_addserver @server=‘SERVER_2’, @local='local', @duplicate_ok= 'duplicate_OK'
go
exit
The old computer name SERVER_1 is deleted, and the new computer name SERVER_2 is added.
3. Restart the SQL Server service in the Windows Service Manager to restore the database.
During IMC installation, the following message is displayed: MS SQLServer is not Installed Correctly, MSSOLSERVER Service Does not Exist. How do I resolve the issue?
The MSSQLSERVER string is the default instance name of the Microsoft SQL Server. This message indicates that you have selected the default instance, but the instance does not exist. If you do not select the default instance, but you specify the instance name ABC, MSSQL$ABC is displayed.
To resolve the issue, check the default instance name in the SQL Server Configuration Manager, and specify the correct instance name during IMC installation.
During IMC installation, the following message is displayed: Database Service MSSQLSERVER Is not Configured to Be Started with Local System. How do I resolve the issue?
To create the database file for IMC, the MSSQLSERVER service must start with the local system and must have write privileges to any local disk. Otherwise, IMC cannot be installed.
For the configuration procedure, see "Changing the SQL Server service startup account."
During IMC installation, the following message is displayed: The ADO 1.5 Component Is not Found in Current System. How do I resolve the issue?
IMC uses ADO 1.5 to connect the database. ADO 1.5 is provided by the operating system.
This message indicates that ADO 1.5 is corrupted. To resolve the issue, reinstall ADO on the host.
During IMC installation, the following message is displayed: Provider Cannot Be Found. How do I resolve the issue?
This message indicates that MDAC is not installed on the server, or that the MDAC installation is corrupted. MDAC corruption typically occurs when application programs attempt to install a partial version of MDAC.
To resolve the issue, download the installation program mdac_typ.exe from the Microsoft website, and then reinstall MDAC. If the MDAC installation fails, perform the following steps:
1. In Windows Explorer, open the C:\WINDOWS\inf folder. (This folder might be hidden.)
2. Right-click the mdac.inf file and select Install.
You can select files from the Service Pack CD or the current operating system.
¡ To select files from the Service Pack CD, locate the i386 directory on the CD drive. For example, if the CD drive is D, select the directory D:\i386.
¡ To select files from the current operating system, click Browse, select a file, and click Retry.
The following files must be located during installation:
- File name: adcjavas.inc
Location: C:\Program Files\Common Files\System\msadc
- File name: adojavas.inc
Location: C:\Program Files\Common Files\System\ado
- File name: msdadc.dll
Location: C:\Program Files\Common Files\System\ole db
- File name: dao360.dll
Location: C:\Program Files\Common Files\Microsoft shared\dao
- File name: handler.reg
Location: C:\Program Files\Common Files\System\msadc
- File name: oledbjvs.inc
Location: C:\Program Files\Common Files\System\ole db
- File name: MDACRdMe.htm
Location: If you cannot locate this file, change the name of the file MDACReadme.htm to MDACRdMe.htm.
3. When the installation is complete, reboot the operating system.
|
|
NOTE: The MDAC installation is successful if no error message is displayed. |
4. If the problem persists, use the MDAC Component Checker to identify MDAC installation problems:
a. Download the MDAC Component Checker cc_pkg.exe from the Microsoft website.
b. Decompress the file to the C:\ComponentChecker directory.
c. In the Component Checker dialog box, select the first option, and then click OK
Figure 61 Component Checker dialog box
After performing the analysis, mismatch information is displayed under File Details. This information indicates potential problems with the MDAC installation.
Figure 62 Mismatch information under File Details
d. Click MISMATCH and view the files in the main pane. These file versions are different from the MDAC version. The Mismatch Field column displays expected file versions. The File Version column displays actual file versions.
5. If the version mismatch information cannot be resolved through MDAC installation, copy files to the corresponding directories.
a. Locate the mdacxpak.cab file from the decompressed file mdac_typ.exe. Use WinZip to decompress the mdacxpak.cab file, which contains most of the important MDAC files.
b. Copy the decompressed files to the corresponding paths displayed in MISMATCH.
c. Reboot the operating system.
6. If you still cannot resolve the issue, reinstall the operating system and databases, or contact Hewlett Packard Enterprise Support.
During IMC installation, the following message is displayed: "Failed to run bcp.exe, Database tools not installed or Windows not restarted" after MS SQL Server installed. How do I resolve the issue?
IMC requires using the bcp.exe tool to access a remote database server. Choose one of the following methods to resolve the issue:
· Method 1: Install the client tool on the SQL Server client, as shown in Figure 63. Restart Windows for the client software bcp.exe to take effect after the installation.
Figure 63 Feature Selection page
· Method 2: Visit https://www.microsoft.com/en-us/download/details.aspx?id=52676 to download and install ODBC driver and MS SQL Cmd Utility on the IMC server, as shown in Figure 64.
Figure 64 Downloading ODBC driver and MS SQL Cmd Utility
How do I update database passwords for IMC?
After the database password of an IMC component is changed using the database management tool, execute pwdmgr.bat to update the password in the file server-addr.xml on the IMC server. The file is located in directory \common\conf in the IMC installation path. It stores database passwords of all IMC components in ciphertext.
The following example uses 192.168.20.107 as the IP address of the database. The dbpassword string represents the new database password of the imc_config user. The config_db string represents the database name. The database IP address and name can be retrieved from the file server-addr.xml.
Figure 65 Updating database passwords for IMC
If IMC is deployed in distributed mode, you must update the database password on every IMC server.
Why can't I install SQL Server on a Microsoft Gold Standard server?
To install SQL Server on a Microsoft Gold Standard server, make sure you are a system user with the proper privileges.
|
Local policy object display name |
User privilege |
|
Backup files and directories |
SeBackupPrivilege |
|
Debug programs |
SeDebugPrivilege |
|
Manage auditing and security log |
SeSecurityPrivilege |
