SQL Server Setup Guide for BusinessObjects Planning

Transcription

1 SQL Server Setup Guide for BusinessObjects Planning BusinessObjects Planning XI Release 2

2 Copyright 2007 Business Objects. All rights reserved. Business Objects owns the following U.S. patents, which may cover products that are offered and licensed by Business Objects: 5,555,403; 6,247,008; 6,289,352; 6,490,593; 6,578,027; 6,768,986; 6,772,409; 6,831,668; 6,882,998 and 7,139,766. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Xcelsius, Crystal Decisions, Intelligent Question, Desktop Intelligence, Crystal Enterprise, Crystal Analysis, Web Intelligence, RapidMarts, and BusinessQuery are trademarks or registered trademarks of Business Objects in the United States and/or other countries. All other names mentioned herein may be trademarks of their respective owners. Third-party Contributors Business Objects products in this release may contain redistributions of software licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at:

3 Contents Chapter 1 Introduction 5 About this guide...6 Who should read this guide...6 Technical requirements...6 SQL Server user interface differences...6 Chapter 2 SQL Server Installation Requirements 7 Using existing SQL Server installations...8 Requirements for new SQL Server installations...8 Chapter 3 Configuring the Planning Database in SQL Server 9 Server configuration...10 Creating the login user...10 Creating the database transfer and backup devices...11 Restoring the original BusinessObjects Planning database...12 Restoring a database in SQL Server Restoring a database in SQL Server Configuring user and database settings...14 Configuring user rights and ownership...14 Configuring database options...15 Chapter 4 Additional Configuration and Administration Considerations 17 Backing up the database...18 Recommended operating system settings...18 Configuring performance and virtual memory...18 SQL Server Setup Guide for BusinessObjects Planning 3

4 Contents Windows 2003 Server...18 Windows 2000 Server...19 Configuring server memory access...19 Recommended SQL Server configuration settings...20 Index 23 4 SQL Server Setup Guide for BusinessObjects Planning

5 Introduction 1

6 Introduction 1 About this guide About this guide This manual provides information necessary for the setup and administration of Microsoft SQL Server for use with BusinessObjects Planning. This document applies to all supported versions of SQL Server. Differences in setup requirements and recommendations are noted in the text. Who should read this guide Installation, configuration and administration of SQL Server is typically handled by the organization's Information Technology department. BusinessObjects Planning Support is also available to assist you with issues relating to use of SQL Server with BusinessObjects Planning. Technical requirements BusinessObjects Planning is supported for use with the following SQL Server versions. SQL Server 2005 SQL Server 2000 (Service Pack 4 or latest, version or higher) Both Standard and Enterprise Editions of the above versions are supported. The recommended client and server hardware and software requirements are outlined in the separately produced document entitled BusinessObjects Planning Technical Requirements. Please contact the BusinessObjects Planning Support department or visit for a copy of the most recent version. SQL Server user interface differences SQL Server 2005 has a different user interface than SQL Server In 2000, dialog boxes are organized by tabs along the top of the dialog. In 2005, dialog boxes are organized by "pages" along the left side of the dialog. In many cases, the names of the tabs and the pages are the same and present similar options. This document uses the convention of "tab" to refer to either the tab or the page, except where 2005 is specifically discussed. 6 SQL Server Setup Guide for BusinessObjects Planning

7 SQL Server Installation Requirements 2

8 SQL Server Installation Requirements 2 Using existing SQL Server installations Using existing SQL Server installations Any existing SQL Server 2000 or 2005 installation that meets the supported version requirements can be used with BusinessObjects Planning. All BusinessObjects Planning databases default to the following data settings. If you need a data set with different settings, please contact your BusinessObjects Planning consultant as soon as possible. Data Type Unicode Data Settings In 2000: Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive In 2005: Latin1_General_CI_AS Non-Unicode Data SQL Server Sort Order 52 on Code Page 1252 Requirements for new SQL Server installations If you are performing a new install of SQL Server 2000 or 2005, there are certain choices you should make to ensure that the installation will be compatible with BusinessObjects Planning. These settings are detailed in the following table. Installation Choices Services Accounts / Service Settings Authentication Mode Collation Settings Required Setting Choose Use a Domain User account (this setting is preferred, but not required). Choose Mixed Mode (Windows Authentication and SQL Server Authentication). Choose SQL Collations with Dictionary order, case-insensitive for use with the 1252 character set. 8 SQL Server Setup Guide for BusinessObjects Planning

9 Configuring the Planning Database in SQL Server 3

10 Configuring the Planning Database in SQL Server 3 Server configuration This chapter explains the process of configuring the BusinessObjects Planning database in SQL Server. This chapter applies to all supported versions of SQL Server except where differences are noted in the text. To configure the BusinessObjects Planning database, you will need to perform the following activities: Create the srcadmin login user. Create the database transfer and backup devices. Restore the BusinessObjects Planning database. Configure the user and database settings. Please consult the SQL Server documentation for full instructions on these activities. The following sections provide an overview and detail the key configuration parameters. Note: During this process, you will need to input a password for the BusinessObjects Planning Admin account. If the password has not already been communicated to you, contact your BusinessObjects Planning implementation consultant or Support to obtain it. Server configuration There are two crucial components to any SQL Server database: the log file and the data file. If possible, these components should reside on two physically independent hard drives or on two fast RAID-5 /10 arrays. The log file is a sequentially written file, whereas the data file access is characterized by random reads and writes. Separating these components on different physical devices allows the disk controller to write data faster. (According to Microsoft technical support, your system will perform even faster up to 30% with two separate SCSI controllers controlling the two physical devices.) Note: The examples in this chapter assume that the SQL Server database has two physical hard drives, and that the operating system is on drive C. The BusinessObjects Planning log file is assumed to be located on C. Drive D contains the master database and the BusinessObjects Planning data file. Creating the login user 1. Open the Security folder, right-click on Logins and then select New Login. 10 SQL Server Setup Guide for BusinessObjects Planning

11 Configuring the Planning Database in SQL Server Creating the database transfer and backup devices 2. Use the following settings on the General tab. Remember that dialogs in SQL Server 2005 are presented using pages instead of tabs, but the page names and settings are otherwise essentially the same. 3 Option Name Authentication Password Setting srcadmin SQL Server authentication Contact your BusinessObjects Planning consultant or Support for the password. Note: In SQL Server 2005, do not select Enforce Password Policy. Database Language master <Default> 3. On the Server Roles tab, make sure that no permissions are selected. Creating the database transfer and backup devices To prepare to restore the BusinessObjects Planning database created by your implementation consultant into your SQL Server environment, create two backup devices one to restore the database, and one to back up the database. 1. Using Windows Explorer, create a new directory on the SQL Server. The examples in this chapter use a directory on the D drive named D:\SQLDA TA. 2. Create two database backup devices: one named SQLBackup, and one named SQLTransfer. These devices should be saved to the backup directory created in the previous step (for example: D:\SQLDATA\Back up\sqltransfer.bak). The method of creating a backup device differs slightly depending on whether you are using SQL Server 2000 or SQL Server 2005: SQL Server Setup Guide for BusinessObjects Planning 11

12 Configuring the Planning Database in SQL Server 3 Restoring the original BusinessObjects Planning database In SQL Server 2005, open the Server Objects folder, right-click Backup Devices and select New Backup Device. In SQL Server 2000, open the Management folder, right-click Backup and select New Backup Device. Restoring the original BusinessObjects Planning database After creating the backup devices, you must restore the BusinessObjects Planning database provided by your implementation consultant.the BusinessObjects Planning database is named SQLTransfer.bak. First, save the SQLTransfer.bak file into the directory where you created the backup devices (for example: D:\SQLData\Backup). Then follow the restoration steps as appropriate for your SQL Server version. Although the steps are similar, the option names are different enough to warrant separate instructions for clarity. Restoring a database in SQL Server 2005 To restore SQLTransfer.bak in SQL Server 2005: 1. Right-click on the Databases folder and select Restore Database. 2. On the General page, use the following settings: Option To database Source for restore Device Restore Setting Planning From device Select the SQLTransfer.bak device checked 3. On the Options page, use the following settings: 12 SQL Server Setup Guide for BusinessObjects Planning

13 Configuring the Planning Database in SQL Server Restoring the original BusinessObjects Planning database 3 Option Restore option Setting Overwrite the existing database Restore as: (see note) Planning Planning_Log Recovery State D:\SQLData\Planning.mdf C:\SQLLog\Planning.ldf Leave the database ready to use by rolling back uncommitted transactions...(restore WITH RECOVERY) Note: Although the logical file names cannot be changed, you can edit the physical path to place the files in a different location. For example, your C drive might not have enough room for the log file, in which case you might place the file on the E drive. Restoring a database in SQL Server 2000 To restore SQLTransfer.bak in SQL Server 2000: 1. Right-click on the Databases folder, select All Tasks and then select Restore Database. 2. On the General tab, use the following settings: Option Restore as database Restore Devices Backup number Restore backup set Database - complete Setting Planning From device Select the SQLTransfer.bak device 1 selected selected SQL Server Setup Guide for BusinessObjects Planning 13

14 Configuring the Planning Database in SQL Server 3 Configuring user and database settings 3. On the Options tab, use the following settings: Option Force restore over existing database Setting Checked Restore database file as: (see note) Planning_Data Planning_Log Recovery completion state D:\SQLData\Planning.mdf C:\SQLLog\Planning_Log.ldf Leave database operational. No additional transaction logs can be restored. Note: Although the logical file names cannot be changed, you can edit the physical path to place the files in a different location. For example, your C drive might not have enough room for the log file, in which case you might place the file on the E drive. Configuring user and database settings After the restore is complete, all settings should be verified for accuracy and some settings must be changed. Configuring user rights and ownership To verify srcadmin's user rights and change ownership of the database: 1. Make sure that no account permissions have been assigned to the Planning database for the srcadmin account. To do so, open the Security folder, click Logins, and select the srcadmin account. Verify the following settings: On the Server Roles tab, verify that no server roles are checked for database Planning. On the User Mapping page (SQL Server 2005 only), verify that only the public role is checked for the master database and the Planning database. 14 SQL Server Setup Guide for BusinessObjects Planning

15 On the Database Access tab (SQL Server 2000 only), verify that database Planning is not checked for user srcadmin. 2. Open the SQL Server Query Analyzer and run the following query with the Planning database selected: sp_changedbowner 'srcadmin' Configuring the Planning Database in SQL Server Configuring user and database settings The database is now owned by srcadmin, and the account does not have any defined server roles. To verify, go back to the srcadmin login and see which permissions are checked. The only permissions that should be checked are the following: In SQL Server 2005: map for the Planning database and with dbo as the assigned user and default schema. In SQL Server 2000: permit for the Planning database and with dbo as the assigned user. 3 Configuring database options The following database options should be verified: 1. Open the Databases folder, right-click on the Planning database and select Properties. 2. Verify the following settings on the Options tab. The settings vary by SQL Server version, as detailed below. Table 3-6: SQL Server 2005 Option Recovery Model Auto Create Statistics Auto Update Statistics Setting Simple True True All other options should be left at the default setting. SQL Server Setup Guide for BusinessObjects Planning 15

16 Configuring the Planning Database in SQL Server 3 Configuring user and database settings Table 3-7: SQL Server 2000 Option Recovery Model Auto Create Statistics Auto Update Statistics Setting Simple checked checked No other options should be checked on this dialog. Note: If you choose not to set Recovery Model to Simple, the log size should be set much larger. You should carefully monitor the available log space, as it can fill up quite rapidly with certain log transactions. You should also automatically schedule the backup and truncation of the log file. Please refer to the SQL Server documentation for information related to automated scheduling and transaction log truncation. 16 SQL Server Setup Guide for BusinessObjects Planning

17 Additional Configuration and Administration Considerations 4

18 Additional Configuration and Administration Considerations 4 Backing up the database Backing up the database Business Objects recommends backing up the Planning database in coordination with your normal backup activities. Please consult your SQL Server documentation for information on backup procedures. Note: Most standard file system backups do not back up in-use files, such as those associated with a SQL Server database. You should configure a process where the SQL Server database is copied to a separate backup file, which can then be backed up as normal (since it is not in use). Recommended operating system settings The following operating system settings are recommended for optimal performance with SQL Server and BusinessObjects Planning. Configuring performance and virtual memory Performance should be set so that all applications are running on the same priority, regardless of whether they are foreground or background applications. Additionally, no virtual memory should be set up on the drive that contains the SQL Server data. The following sections explain where to configure these options within each operating system. Windows 2003 Server To configure the performance and virtual memory settings in Windows 2003 Server: 1. Go to Control Panel > System and select the Advanced tab. 2. In the Performance section, click Settings to open the Performance Options dialog. 3. On the Advanced tab, verify or change the following settings, then click Apply: Option Processor Scheduling Setting Background Services 18 SQL Server Setup Guide for BusinessObjects Planning

19 Additional Configuration and Administration Considerations Recommended operating system settings 4 Option Memory Usage Virtual Memory Setting System Cache Click Change to view the virtual memory settings. Verify that no virtual memory is set up on the data drive (drive D in the examples in this document). Windows 2000 Server To configure the performance and virtual memory settings in Windows 2000 Server: 1. Go to Control Panel > System and select the Advanced tab. 2. In the Performance section, click Performance Settings to open the Performance Options dialog. Verify or change the following settings on this dialog: Option Optimize performance for Virtual Memory Setting Background Services Click Change to view the virtual memory settings. Verify that no virtual memory is set up on the data drive (drive D in the examples in this document). Configuring server memory access The server should be configured so that SQL Server has maximum access to the server's memory. These instructions apply to both Windows 2003 Server and Windows 2000 Server: 1. Go to Control Panel > Network Connections > Local Area Connection, then click Properties. (Note: in Windows 2000 Server, the menu item is named Network and Dial-Up Connections.) SQL Server Setup Guide for BusinessObjects Planning 19

20 Additional Configuration and Administration Considerations 4 Recommended SQL Server configuration settings 2. On the General tab, click File and Printer Sharing for Microsoft Networks and then click Properties. 3. Select Maximize Throughput for Network Applications. Also, verify that Make Browser Broadcasts to LAN Manager 2.x Clients is not selected (unless the server does have LAN Manager 2.x clients connecting to it). Recommended SQL Server configuration settings SQL Server has robust default configuration settings. A few minor changes to these settings are recommended for optimal use with BusinessObjects Planning. After changing the settings, restart the SQL Server. 1. To edit the configuration settings, right-click on the SQL Server name in Management Studio (2005) or Enterprise Manager (2000) and select Properties. 2. On the Processor tab, verify or change the following settings: Table 4-3: SQL Server 2000 Options Processor Boost SQL Server priority on Windows Use all available processors Settings Make sure that all processors listed are checked for use. checked checked Table 4-4: SQL Server 2005 Options Automatically set processor affinity mask for all processors Automatically set I/O affinity mask for all processors Settings checked checked 20 SQL Server Setup Guide for BusinessObjects Planning

21 Additional Configuration and Administration Considerations Recommended SQL Server configuration settings 4 Options Maximum worker threads Boost SQL Server Priority Settings 0 checked 3. For SQL 2000, click on the Memory tab, and verify that Dynamically configure SQL Server is selected. SQL Server Setup Guide for BusinessObjects Planning 21

22 Additional Configuration and Administration Considerations 4 Recommended SQL Server configuration settings 22 SQL Server Setup Guide for BusinessObjects Planning

23 Index B backing up the database 18 backup device creating 11 D data file 10 database backing up 18 configuring 15 ownership 14 password 10 restoring the original BusinessObjects Planning database 12 E existing installations of SQL Server, requirements 8 I installation parameters SQL Server SQL Server intended audience 6 L log file 10 size considerations 15 login user creating 10 rights 14 N Non-Unicode Data settings SQL Server SQL Server P password for the Planning database 10 performance settings configuring 18 S server configuration 10 SQL Server 11 configuration settings 20 Memory settings 20 Processor settings 20 restoring the original BusinessObjects Planning database 12 supported versions 6 user interface differences between versions 6 SQL Server 2000 required installation parameters 8 Unicode Data settings 8 utilizing existing implementations 8 SQL Server 2005 required installation parameters 8 SQL Server Setup Guide for BusinessObjects Planning 23

24 Index SQL Server 2005 (continued) restoring the original BusinessObjects Planning database 12, 13 Unicode Data settings 8 utilizing existing implementations 8 SQLTRANSFER.BAK 12 srcadmin account permissions 14 creating 10 SRCBackup 11 SRCTransfer 11 supported SQL Server versions 6 T technical requirements 6 transfer device creating 11 U Unicode Data settings SQL Server SQL Server V virtual memory configuring 18 W Windows 2000 Server memory access settings 19 performance settings 19 virtual memory settings 19 Windows 2003 Server memory access settings 19 performance settings 18 virtual memory settings SQL Server Setup Guide for BusinessObjects Planning