SQL Server Installation and Configuration Guide. Abstract

Transcription

1 SQL Server 2008 Installation and Configuration Guide Abstract This document describes the configuration during and after database installation when IMC is used together with Microsoft SQL Server. The document is applicable to the SQL Server 2008 SP3 Enterprise edition and slightly different from the prior editions. This document is intended for use by network engineers or system administrators responsible for installing network software and components. Part number: Software version: IMC PLAT 5.1 (E0202) Document version: 5P

2 Legal and notice information Acknowledgments Copyright Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Oracle and Java are registered trademarks of Oracle and/or its affiliates.

3 Contents 1 Installing SQL Server Registering the SQL server license 25 3 Installing SQL Server client 27 4 Setting Up SQL Server Configuring TCP/IP properties 35 Configuring the SQL Server service to Log on as local system 37 Restarting the SQL Server service 39 Creating a super user and granting a privilege to the user 40 5 Uninstalling SQL Server database 44 6 FAQs 45 7 Support and other resources 51 Contacting HP 51 Subscription service 51 Related information 51 Documents 51 Websites 51 Conventions 52 Index 53 i

4 1 Installing SQL Server 2008 Before installing IMC, install SQL Server first. After installing SQL Server, restart the operating system, update the server with latest Windows patches and then proceed to install IMC. Currently, you can install the database on a separate database server and save the IMC data on the database server. To install the database on a separate database server, follow these guidelines: On the IMC server, install an SQL Server client with the same version as the database. Create a data file folder on the database server before you start the installation. When deploying the IMC components, you can input the local path to the folder, as shown in Figure 1 (page 2). Figure 1 IMC installation-database Configuration Info NOTE: To ensure the normal operation of SQL Server, use a licensed installation software of Microsoft SQL Server. Using the localized software or other unauthorized editions may cause a failure in database installation and operation. SQL Server 2008 cannot be installed on Windows 2008 R2. After running the setup program, enter the SQL Server Installation Center, as shown in Figure 2 (page 3). 2

5 Figure 2 SQL Server Installation Center Select Installation from the navigation tree, and then click New SQL Server stand-alone installation or add features to an existing installation to enter the Product Key dialog box, as shown in Figure 3 (page 4). 3

6 Figure 3 Product Key dialog box Input the product key and click Next to enter the License Terms dialog box, as shown in Figure 4 (page 5). 4

7 Figure 4 License Terms dialog box Select I accept the license terms, and click Next to enter the Setup Support Files dialog box, as shown in Figure 5 (page 6). 5

8 Figure 5 Setup Support Files dialog box Click Install to start installing setup support files. The setup support files dialog box appears, as shown in Figure 6 (page 7). 6

9 Figure 6 Setup Support Files operation process Upon completion of the installation, the Setup Support Rules dialog box appears, as shown in Figure 7 (page 8). 7

10 Figure 7 Setup Support Rules dialog box Click Next to enter the Feature Selection dialog box, as shown in Figure 8 (page 9). 8

11 Figure 8 Feature Selection dialog box Select the features shown in the above figure, and then click Next to enter the Instance Configuration dialog box, as shown in Figure 9 (page 10). 9

12 Figure 9 Instance Configuration dialog box Select Default instance and use MSSQLSERVER as the Instance ID. To change the current instance ID, select Named instance and then enter a new instance ID. If you install the SQL Server 2008 Express SP1 edition, select Named instance. Click Next to enter the Disk Space Requirements dialog box, as shown in Figure 10 (page 11). 10

13 Figure 10 Disk Space Requirements dialog box Click Next to enter the Server Configuration dialog box, shown in Figure 11 (page 12). 11

14 Figure 11 Server Configuration dialog box Click Use the same account for all SQL Server services to set a service account. Select account NT AUTHORITY\SYSTEM, as shown in Figure 12 (page 12). Figure 12 Use the same account for all SQL Server 2008 services dialog box Make sure to use the account name under the Local system. Then click OK to go back to the server configuration dialog box, as shown in Figure 13 (page 13). 12

15 Figure 13 Server Configuration dialog box Click Collation, as shown in Figure 14 (page 14). 13

16 Figure 14 Collation tab page Without any configuration on the Collation tab page, click Next to enter the Database Engine Configuration dialog box, shown in Figure 15 (page 15). 14

17 Figure 15 Database Engine Configuration dialog box Configure the Authentication Mode as Mixed Mode and input the password of user sa. SQL Server 2008 has certain requirements for password complexity. For information about password complexity, see the online help in the system. Furthermore, you can specify an SQL Server administrator according to the actual conditions, as shown in Figure 16 (page 16). IMPORTANT: For IMC to correctly identify the sa logon password during installation, make sure that the password does not contain any of the following characters: < > \t If you do not want to change the password of the sa user, create a user with sa user privileges and make sure that the password does not contain any of the previous characters. For more information about creating a database user, see Creating a super user and granting a privilege to the user (page 40). 15

18 Figure 16 Specify SQL Server administrators The Data Directions, shown in Figure 17 (page 17) and FILESTREAM, shown in Figure 18 (page 18) use the default values without any configuration. 16

19 Figure 17 Data Directories tab page The FILESTREAM tab page is shown in Figure 18 (page 18). 17

20 Figure 18 FILESTREAM tab page Click Next to enter the Error and Usage Reporting dialog box, shown in Figure 19 (page 19). 18

21 Figure 19 Error and Usage Reporting dialog box Without any configuration, click Next to enter the Installation Rules dialog box, shown in Figure 20 (page 20). 19

22 Figure 20 Installation Rules dialog box Click Next to enter the Ready to Install dialog box, as shown in Figure 21 (page 21). 20

23 Figure 21 Ready to Install dialog box Click Install to enter the Installation Progress dialog box, as shown in Figure 22 (page 22). 21

24 Figure 22 Installation Progress dialog box The components installed are relevant to the features selected previously. Figure 23 (page 23) shows the setup operation complete. 22

25 Figure 23 Setup operation completion Upon completion of the installation, click Next to enter the Complete dialog box, as shown in Figure 24 (page 24). 23

26 Click Close to close the Complete dialog box. Figure 24 Complete dialog box 24

27 2 Registering the SQL server license The SQL server supports three license registration modes: Per Processor, Server/Client Access License (CAL), and Per User. The Per Processor is used for registering the SQL Server 2008 R2 Developer and Parallel Data Warehouse. This chapter describes the registration modes of Per Processor and Server/CAL. Per Processor licensing: The number of Per Processor licenses is counted by the number of processors on an SQL server. You must buy a Per Processor license for each processor on a server installed with the SQL server component. The Per Processor registration mode is irrelevant to the number of SQL servers and IMC servers, and is applicable to the networks containing a lot of SQL servers and IMC servers. See Figure 25 (page 25) for an example. Figure 25 Per Processor Licensing NOTE: The number of the Per Processor licenses is irrelevant to the number of kernels in a processor. Server/CAL licensing: The number of Server/CAL licenses is counted 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. The Server/CAL registration mode is applicable to the networks containing a few SQL servers and IMC servers. See Figure 26 (page 26) for an example of CAL licensing. 25

28 Figure 26 Server/CAL Licensing Before you choose a registration mode, determine the IMC deployment environment: When IMC is deployed in centralized mode, buy a CAL license for only the IMC server. When IMC is deployed in distributed mode, buy a CAL license for each IMC server that needs to access the SQL server. NOTE: The application of the license registration modes is for SQL Server 2005/2008/2008 R2 of standard and enterprise editions. You do not need to buy a license for the SQL Server Express edition. For more information about SQL server license registration, see official Microsoft documents. 26

29 3 Installing SQL Server client If you install the database separately, that is, install an IMC server and a database server on different hosts, you need to install the SQL Server client with the same version as the database on the IMC server. On the Feature Selection dialog box, select client components, as shown in Figure 27 (page 27). See Installing SQL Server 2008 (page 2) for how to enter the Feature Selection dialog box. Figure 27 Feature Selection dialog box Select the features (Management Tools Basic and SQL Client Connectivity SDK) shown in the above figure, and then click Next to enter the Disk Space Requirements dialog box, as shown in Figure 28 (page 28). 27

30 Figure 28 Disk Space Requirements dialog box Click Next to enter the Error and Usage Reporting dialog box, as shown in Figure 29 (page 29). 28

31 Figure 29 Error and Usage Reporting dialog box Without any configuration, click Next to enter the Installation Rules dialog box, as shown in Figure 30 (page 30). 29

32 Figure 30 Installation Rules dialog box Click Next to enter the Ready to Install dialog box, shown in Figure 31 (page 31). 30

33 Figure 31 Ready to Install dialog box Click Install to enter the Installation Progress dialog box, as shown in Figure 32 (page 32). 31

34 Figure 32 Installation Progress dialog box The components installed are relevant to the features selected previously. When the installation process is complete the setup operation completion dialog box appears, as shown in Figure 33 (page 33). 32

35 Figure 33 Setup operation completion Upon completion of the installation, click Next to enter the Complete dialog box, as shown in Figure 34 (page 34). 33

36 Click Close to close the Complete dialog box. Figure 34 Complete dialog box 34

37 4 Setting Up SQL Server 2008 This chapter discusses the steps and procedures to setup and configure an SQL Server. This includes: Configuring TCP/IP Configuring the SQL Server service Restarting the SQL Server service Creating a super user Configuring TCP/IP properties Select Start All Programs Microsoft SQL Server 2008 Configuration Tools SQL Server Configuration Manager, as shown in Figure 35 (page 35) and Figure 36 (page 35). Figure 35 SQL Server Configuration Manager Figure 36 SQL Server Configuration Manager window On the SQL Server Configuration Manager window, select SQL Server Network Configuration Protocols for MSSQLSERVER from the navigation tree, and then double-click TCP/IP on the right (or click TCP/IP and then click the Properties icon on the toolbar). 35

38 The TCP/IP Properties dialog box appears, as shown in Figure 37 (page 36). Figure 37 Configure TCP/IP Properties On the Protocol tab page, make sure Yes is selected for Listen All; on the IP Address tab page, select Yes for the Enabled option of each IP address, and change TCP Port to 1433, as shown in Figure 38 (page 37). 36

39 Figure 38 Configure IP addresses for TCP/IP Click OK to save the configuration. Click OK when the message box saying Changes to TCP/IP properties do not take effect until you restart the service appears. NOTE: If you did not select Yes for Listen All on the TCP/IP Properties dialog box, enter the dialog box to update the previously-configured IP addresses if the server IP address changes after installing SQL Server Otherwise, you cannot connect to the database. You can use the same way to enable the Named Pipes property. Configuring the SQL Server service to Log on as local system On the SQL Server Configuration Manager window, select SQL Server Services from the navigation tree, and you can see the operational status of SQL Server services on the right, as shown in Figure 39 (page 38). 37

40 Figure 39 Operational status of SQL Server services Check the Log On As column of the SQL Server, and make sure its value is Local System. The value is sure to be Local System if you strictly follow the installation steps mentioned above. If you did not strictly follow the installation steps mentioned above, the value may be Network Service. In this case, you should change it to Local System, with the procedure as follows: double-click the row (or select the row and then click the Properties icon on the toolbar), and the SQL Server Properties dialog box appears. On the dialog box, change the Log on as property into Local System in the Built-in account option, as shown in Figure 40 (page 39). 38

41 Figure 40 Configure the Log on as property on the SQL Server Properties dialog box After the change, click OK to save the configuration. Restarting the SQL Server service After completing the preceding configurations, you must restart the SQL Server service to make the configurations take effect. On the SQL Server Configuration Manager window, select SQL Server Services from the navigation tree, select SQL Server (MSSQLSERVER) on the right, and then click Restart service on the toolbar, as shown in Figure 41 (page 40). 39

42 Figure 41 Restart the SQL Server Service The reboot of the Windows operating system can automatically restart all the services. As the reboot of the operating system is required for installing IMC after the SQL Server installation is completed, you do not need to restart the SQL Server service separately. Creating a super user and granting a privilege to the user When installing IMC, you must use a super user to access the database. The super user can be the default user sa or a user-defined super user. This chapter describes how to create a super user and grant the administrator privilege to it. Select Start All programs Microsoft SQL Server 2008 SQL Server Management Studio. The database login window appears, as shown in Figure 42 (page 41). 40

43 Figure 42 Login interface Select SQL Server Authentication for Authentication, select a login username, enter the password, and click Connect. Expand the Security node in the navigation tree, right-click Logins, and select New Login from the shortcut menu. The following menu screen appears, Figure 43 (page 41). Figure 43 Microsoft SQL Server Management Studio main pane 41

44 The Add a login user dialog box appears, as shown in Figure 44 (page 42). Figure 44 Add a login user Set the login name, click SQL Server authentication, and set the password. IMPORTANT: For IMC to correctly identify the password, make sure that the password does not contain any of the following characters: < > \t Clear the User must change password at next login box and select Server Roles in the navigation tree to set the server roles, as shown in Figure 45 (page 43). 42

45 Figure 45 Set server roles Select sysadmin and click OK. The user is granted with the database administrator privilege. After the previous operations, the new user can be seen under the Security Logins node in the navigation tree of the Microsoft SQL Server Management Studio main pane. 43

46 5 Uninstalling SQL Server database If you uninstall the SQL Server database with the Remove function on the Control Panel Add or Remove Programs page, you may fail to uninstall the database (the setup.exe process hangs) because of operating system configuration problems. As a solution, you can use the Change function to uninstall the database, as shown in Figure 46 (page 44). Figure 46 Uninstall SQL Server 2008 with the Change function 44

47 6 FAQs Does changing the computer name affect the database? How to restore the database? Changing a computer name may cause some failures on operating SQL Server database. In this case, perform the following operations to update the computer name saved in the database: Suppose the old computer name is SERVER_1 and the new one is SERVER_2. Open cmd.exe of Windows and execute the following scripts (assuming that the login user name is sa and the password is imcpass): osql -Usa -PiMCpass go The old computer name SERVER_1 is displayed on the interface. Continue to execute the following commands to modify the computer name saved in the database: go SERVER_2, 'duplicate_ok' go exit The commands above first delete the old computer name SERVER_1 and then add a new one SERVER_2. After the modification above, you must restart the SQL Server service in the Windows Service Manager to restore the database. During the IMC installation, "MS SQLServer is not installed correctly, MSSOLSERVER Service Does not Exist" is displayed. What shall I do? MSSQLSERVER is the default instance name of the Microsoft SQL Server. Displaying MSSQLSERVER means you have selected the default instance. If you do not select the default instance but specify an instance name ABC, MSSQL$ABC is displayed. To view the correct instance name, make sure the default instance or the specified instance name exists in the SQL Server Configuration Manager. During the IMC installation, "Database Service MSSQLSERVER Is not Configured to Be Started with Local System" is displayed. What shall I do? During the installation, IMC needs to create its own database file. If the MSSQLSERVER service is not configured to run as the Local System, IMC fails to install because of the disc access restriction. To solve the problem, do as follows: Select Start All Programs Microsoft SQL Server 2008 Configuration Tools SQL Server Configuration Manager as shown in Figure 47 (page 46). 45

48 Figure 47 Select the SQL Server Configuration Manager from the Start menu Right-click SQL Server (MSSQLSERVER) on the SQL Server Configuration Manager window and select Properties, as shown in Figure 48 (page 46). Figure 48 SQL Server Configuration Manager window On the SQL Server (MSSQLSERVER) Properties window, click Built-in account, select Local System from the list, and then click OK, as shown in Figure 49 (page 47). 46

49 Figure 49 SQL Server (MSSQLSERVER) Properties window After completing the preceding configurations, you need to restart the SQL Server (MSSQLSERVER) service on the SQL Server Configuration Manager window. After that, configurations take effect. During the IMC installation, "The ADO1.5 Component Is not Found in Current System" is displayed. What shall I do? IMC uses ADO 1.5 to connect the database. ADO 1.5 is provided by the operating system. This error indicates that ADO 1.5 is corrupted. To solve the problem, you can re-install ADO. During the IMC installation, "Provider Cannot Be Found" is displayed. What shall I do? This error means that MDAC is not installed on the server or that your MDAC installation is corrupted. MDAC corruption usually occurs when some application programs erroneously attempt to install a partial version of MDAC. To solve the problem, you can download the installation program mdac_typ.exe from Microsoft's website to re-install MDAC. If MDAC installation fails, you can do as follows: 1. In Windows Explorer, open the C:\WINDOWS\inf folder. Note that the folder may be hidden. 2. Right-click the mdac.inf file in the folder and select Install. You can select each file from Service Pack CD-ROM, or from the current operating system. If you want to select files from Service Pack CD-ROM, locate the i386 directory from the CD-ROM drive. For example, if the CD-ROM drive is D:, you need to select the D:\i386 directory. If you want to select files from the current operating system, click Browse to select files. Select a file and click Retry. 3. MDAC is installed successfully if no error is displayed after you complete the installation. 47

50 Files to be located during the installation and their locations are as follows: 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 find the MDACRdMe.htm, change the name of the file MDACReadme.htm to MDACRdMe.htm. After the installation, you need to reboot the operating system. If the problem is not solved, you can use the MDAC Component Checker provided by Microsoft to locate MDAC installation problems. Download a free MDAC Component Checker, cc_pkg.exe from the Microsoft website, decompress it to the C:\ComponentChecker directory, click the first button in the window as shown in Figure 50 (page 48), and click OK. Figure 50 Component Checker window After a short time analysis, some information is displayed, as shown in Figure 51 (page 49). Pay attention to the information about MISMATCH under File Details. The MISMATCH information indicates 48

51 the potential problems of the MDAC installation. Figure 51 Information about MISMATCH under File Details Click MISMATCH and view files in the right window. 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. When version mismatch cannot be solved through MDAC installation, you need to copy files to the corresponding directories. Locate the mdacxpak.cab file from the depressed path of MDAC_TYPE.exe and use WinZip to decompress the mdacxpak.cab file. The file contains most of the important MDAC files. Copy the depressed files to corresponding paths shown in MISMATCH. Reboot the operating system. If you still cannot solve the problem, you are recommended to re-install your operating system and databases, or contact the technical support department. During the IMC installation, the system prompts "Failed to run bcp.exe, Database tools not installed or Windows not restarted after MS SQL Server installed". How to solve this problem? When you select to use a remote database server, a server which the business components are not on, IMC needs to use a tool such as bcp.exe to access the database. You should manually install Connectivity Components client tools on the IMC server. For the detailed installation procedures, see the Feature Selection dialog box in Figure 8 (page 9). Additionally, after installing the Connectivity Components, you should restart the Windows to make the client software bcp.exe take effect. How can I update database passwords for IMC? The usernames and passwords used by the IMC modules are stored in cipher text in file \common\conf\ server-addr.xml in the installation path. You can use the pwdmgr.bat command to obtain passwords in clear text or update the latest passwords to the file. Usually, a user can use the database management tool to change the database password of a certain IMC module. To ensure communication between IMC and the database, use the pwdmgr.bat command to update the corresponding password in file server-addr.xml. If IMC is deployed in distributed mode, you must update the password for every IMC server, as shown in Figure 52 (page 50). 49

52 Figure 52 Update database passwords for IMC In the preceding commands, dbpasswd represents the latest database password of the imc_config user, config_db represents the database name, and represents the IP address of the database. To obtain the IP address and name of a SQL Server database, view the settings of the corresponding user in file $IMCROOT/common/conf/server-addr.xml. 50

53 7 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: Before contacting HP, collect the following information: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: An notification is sent to you after registration is completed containing: Product enhancements New driver versions Firmware updates Other product resources Related information Documents Websites To find related documents, browse to the Manuals page of the HP Business Support Center website: For related documentation, navigate to the Networking section, and select a networking category. For a complete list of acronyms and their definitions, see HP A-Series Acronyms. HP.com: HP Networking: HP manuals: HP download drivers and software: 51

54 HP software depot: Conventions This section describes the conventions used in this documentation set. Command conventions Convention Boldface Italic / Description Bold text represents commands and keywords that you enter literally as shown. Italic text represents arguments that you replace with actual values. Multi-level menus are separated by forward slashes. For example, [File/Create/Folder]. GUI conventions Convention Boldface Description Window names, button names, field names, and menu items are in bold text. For example, the New User window appears; click OK. Multi-level menus are separated by arrows. For example, File Create Folder. Symbols Convention WARNING CAUTION NOTE Description An alert that calls attention to important information that if not understood or followed can result in personal injury. An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software. An alert that contains additional or supplementary information. 52

55 Index add a login user, 42 CAL licensing device CAL, 26 user CAL, 26 collation tab page, 14 configuring TCP/IP properties, 35, 36 conventions command, 52 GUI, 52 symbols, 52 data directories page, 17 database engine configuration authentication mode, 15 dialog box, 15 mixed mode, 15 dialog box complete, 24, 34 database engine configuration, 14, 15 disk space requirements, 11, 28 error and usage reporting, 19, 29 feature selection, 9, 27 installation progress, 22, 32 installation rules, 20, 30 instance configuration, 10 license terms, 5 product key, 4 ready to install, 21, 31 same account, 12 server configuration, 12, 13 setup support files, 6 setup support rules, 8 SQL server properties, 39 FAQs, 45 ADO 1.5 components not found, 47 changing the computer name, 45 component checker window, 48 database server not configured, 45 database tools not installed, 49 failed to run, 49 local system, 45 MISMATCH, 49 not configured to be started, 45 provider cannot be found, 47 restoring the database, 45 server does not exist, 45 SQL server configuration manager, 46 SQL server not installed correctly, 45 SQL server properties window, 47 updating passwords, 49 filestream, 18 HP support website, 51 IMC installation, 2 configuration info, 2 database, 2 installation database configuration, 2 navigation tree, 3 installing SQL client, 27 feature selection, 27 IMC installation database, 2 server 2008, 2 IP addresses, 37 license terms dialog box, 5 login interface, 41 MSSQLSERVER database service, 45 default instance, 45 displaying, 45 instance ID, 10 properties, 46 protocols, 35 server configuration manager, 47 SQL server, 39 SQL Server, 46 product key dialog box, 4 registering SQL server license, 25 related information documents, 51 websites, 51 restarting the SQL server service, 40 server license CAL licensing, 26 per processor, 25 registering, 25 SQL server license, 25 server setup, 35 set server roles, 43 setup operation completion, 23, 33 setup support files, 7 53

56 operation process, 7 rules, 7 setup support files dialog box, 6 SQL server administrator, 16 authentication, 42 change function, 44 configuration manager, 35 configuration manager window, 35, 46 installation center, 3 local system, 37 operational status, 38 properties window, 47 restarting service, 39 service, 39 services, 38 setup, 35 uninstalling server database, 44 SQL server management studio, 41 super user creating, 40 granting privileges, 40 support and resources contacting HP, 51 subscription service, 51 TCP/IP configure IP addresses, 37 configuring, 36 properties, 36 uninstalling SQL server database, 44 update database passwords, 50 websites, 51 54