SQL Server Administration Guide

SQL Server Setup Guide for Business Objects Planning

Business Objects Planning XI

Patents Business Objects owns the following U.S. patents, which may cover products that are offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352.

Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners.

Copyright Copyright © 1999-2006 Business Objects. All rights reserved.

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:http://www.businessobjects.com/thirdparty

Contents
Chapter 1 Introduction 5
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Who should read this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Technical requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6SQL Server user interface differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Support contact information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 SQL Server Installation Requirements 9Using existing SQL Server installations . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

SQL Server 2000 or 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10SQL Server 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installing SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10SQL Server 2000 or 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11SQL Server 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3 Configuring the Planning Database in SQL Server 13Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Creating the login user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Creating the database transfer and backup devices . . . . . . . . . . . . . . . . . 15Restoring the original Business Objects Planning database . . . . . . . . . . . 16

Restoring a database in SQL Server 2005 . . . . . . . . . . . . . . . . . . . . . 16Restoring a database in SQL Server 7.0 or 2000 . . . . . . . . . . . . . . . . 17

Configuring user and database settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 18User rights and ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Database options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 4 Additional Configuration and Administration Issues 21Backing up the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

SQL Server Setup Guide for Business Objects Planning 3

Contents

Recommended operating system settings . . . . . . . . . . . . . . . . . . . . . . . . . 22Performance and virtual memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Windows 2003 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Windows 2000 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Windows NT Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Server memory access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Windows 2003 Server and Windows 2000 Server . . . . . . . . . . . . . 24Windows NT Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Recommended SQL Server configuration settings . . . . . . . . . . . . . . . . . . . 24

4 SQL Server Setup Guide for Business Objects Planning

Introduction

cha

pte

r

IntroductionAbout this guide1
About this guide
This manual provides information necessary for the setup and administration of Microsoft® SQL Server for use with Business Objects Planning. Business Objects Planning is supported for use with the following SQL Server versions.• SQL Server 2005• SQL Server 2000 (Service Pack 3 or latest, version 8.00.194 or higher)• SQL Server 7.0 (version 7.00.842 or higher)Both Standard and Enterprise Editions of the above versions are supported.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 guideInstallation, configuration and administration of SQL Server is typically handled by the organization’s Information Technology department. Business Objects Planning Support is also available to assist you with issues relating to use of SQL Server with Business Objects Planning.

Technical requirementsThe recommended client and server hardware and software requirements are outlined in the separately produced document entitled Business Objects Planning Technical Requirements. Please contact the Business Objects Planning Support department or visit www.mysrc.com for a copy of the most recent version.

SQL Server user interface differencesSQL Server 2005 presents a different user interface than 7.0 or 2000. In 7.0 and 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.


http://www.mysrc.com

IntroductionSupport contact information 1

Support contact informationIf you have any questions after consulting this document, please contact Business Objects Planning Support. The contact information is listed in the following table by region.

Region Phone Email

Americas 1 800 544 3477 [email protected] Pacific 65 64166567 [email protected], Middle East and Africa

0800 389 4130 [email protected]


IntroductionSupport contact information1



SQL Server Installation Requirements

cha

pte

r

SQL Server Installation RequirementsUsing existing SQL Server installations2
Using existing SQL Server installations
Business Objects Planning can be used with an existing installation of SQL Server, if the existing installation meets certain requirements.

SQL Server 2000 or 2005Any existing SQL Server 2000 or 2005 installation that meets the supported version requirements can be used. All Business Objects Planning databases default to the following data settings. If you need a data set with different settings, please contact your Business Objects Planning consultant as soon as possible.

SQL Server 7.0Existing installations of SQL Server 7.0 can be used if the installation meets the following conditions:• The Sort Order must be set to Dictionary order, case insensitive.• The Character Set must be set to ISO.• Unicode Collation must be set to General Unicode, with the following

settings:• Case-Insensitive• Accent-Sensitive• Width-Insensitive• Kana-Insensitive

Installing SQL ServerThis section details the required SQL Server installation parameters for Business Objects Planning.

Data Type Settings

Unicode Data • 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


SQL Server Installation RequirementsInstalling SQL Server 2

SQL Server 2000 or 2005Please follow the instructions in the SQL Server documentation to install SQL Server 2000 or 2005. During the install, there are certain choices you should make to ensure that the installation will be compatible with Business Objects Planning. These settings are detailed in the following table.

SQL Server 7.0While SQL Server 7.0 is supported, it is an older version of the product. If you are using SQL Server 7.0, it is most likely an existing installation (“Using existing SQL Server installations” on page 10). Contact Business Objects Planning Support if you need assistance determining appropriate installation choices for SQL Server 7.0.

Installation Choices Required Setting

Services Accounts / Service Settings

Choose Use a Domain User account (this setting is preferred, but not required).

Authentication Mode Choose Mixed Mode (Windows Authentication and SQL Server Authentication).

Collation Settings Choose SQL Collations with Dictionary order, case-insensitive for use with the 1252 character set.


SQL Server Installation RequirementsInstalling SQL Server2



Configuring the Planning Database in SQL Server

cha

pte

r

Configuring the Planning Database in SQL ServerOverview3
Overview
This chapter explains the process of configuring the Business Objects 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 Business Objects Planning database, you will need to perform the following activities:• Create the srcadmin login user.• Create the database transfer and backup devices.• Restore the Business Objects 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 Business Objects Planning Admin account. If the password has not already been communicated to you, contact your Business Objects Planning implementation consultant or Support to obtain it.

Server configurationThere 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 Business Objects Planning log file is assumed to be located on C. Drive D contains the master database and the Business Objects Planning data file.

Creating the login userTo create the srcadmin login user:


Configuring the Planning Database in SQL ServerCreating the database transfer and backup devices 3

1. Open the Security folder, right-click on Logins and then select New Login.

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. On the Server Roles tab, make sure that no permissions are selected.

Creating the database transfer and backup devices

To prepare to restore the Business Objects 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:\SQLDATA.

2. Create two database backup devices: one named SQLBackup, and one named SQLTransfer. These devices should be saved to the backup directory created in Step 1 (for example: D:\SQLDATA\Backup\SQLTransfer.bak).

The method of creating a backup device differs slightly depending on whether you are using SQL Server 7.0 / 2000 or SQL Server 2005:• In SQL Server 2005, open the Server Objects folder, right-click Backup

Devices and select New Backup Device.• In SQL Server 7.0 / 2000, open the Management folder, right-click

Backup and select New Backup Device.

Option Setting

Name srcadminAuthentication SQL Server authenticationPassword Contact your Business Objects Planning consultant

or Support for the password.NOTE: In SQL Server 2005, do not select Enforce Password Policy.

Database master Language <Default>


Configuring the Planning Database in SQL ServerRestoring the original Business Objects Planning database3
Restoring the original Business Objects Planning database
After creating the backup devices, you must restore the Business Objects Planning database provided by your implementation consultant.The Business Objects 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 2005To 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:

3. On the Options page, use the following settings:

Option Setting

To database SRCIASource for restore From deviceDevice Select the SQLTransfer.bak

device Restore checked

Option Setting

Restore option Overwrite the existing databaseRestore as: (see note)SRCIA D:\SQLData\SRCIA.mdf

SRCIA_Log C:\SQLLog\SRCIA.ldf

Recovery State Leave the database ready to use by rolling back uncommitted transactions....(RESTORE WITH RECOVERY)


Configuring the Planning Database in SQL ServerRestoring the original Business Objects Planning database 3

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 7.0 or 2000To restore SQLTransfer.bak in SQL Server 7.0 or 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:

3. On the Options tab, use the following settings:

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.

Option Setting

Restore as database SRCIARestore From deviceDevices Select the SQLTransfer.bak

device Backup number 1Restore backup set selectedDatabase - complete selected

Option Setting

Force restore over existing database

Checked

Restore database file as: (see note)SRCIA_Data D:\SQLData\SRCIA.mdf

SRCIA_Log C:\SQLLog\SRCIA_Log.ldf

Recovery completion state Leave database operational. No additional transaction logs can be restored.


Configuring the Planning Database in SQL ServerConfiguring user and database settings3
Configuring user and database settings
After the restore is complete, all settings should be verified for accuracy and some settings must be changed.

User rights and ownershipTo verify srcadmin’s user rights and change ownership of the database:1. Make sure that no account permissions have been assigned to the

SRCIA 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 SRCIA.• On the User Mapping page (SQL Server 2005 only), verify that only

the public role is checked for the master database and the SRCIA database.

• On the Database Access tab (SQL Server 7.0 / 2000 only), verify that database SRCIA is not checked for user srcadmin.

2. Open the SQL Server Query Analyzer and run the following query with the SRCIA database selected:sp_changedbowner ‘srcadmin’

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 SRCIA database and with dbo as the

assigned user and default schema.• In SQL Server 7.0 /2000: permit for the SRCIA database and with dbo

as the assigned user.

Database optionsThe following database options should be verified:1. Open the Databases folder, right-click on the SRCIA database and

select Properties. 2. Verify the following settings on the Options tab. The settings vary by

SQL Server version, as detailed below.


Configuring the Planning Database in SQL ServerConfiguring user and database settings 3

SQL Server 2005

SQL Server 2000

SQL Server 7.0

The Recovery Model: Simple option and the Truncate Log on Checkpoint option are essentially the same. If you choose not to enable this option, 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.

Option Setting

Recovery Model SimpleAuto Create Statistics TrueAuto Update Statistics TrueAll other options should be left at the default setting.

Option Setting

Recovery Model SimpleAuto Create Statistics checkedAuto Update Statistics checkedNo other options should be checked on this dialog.

Option Setting

Select into / bulk copy checkedTruncate Log on Checkpoint checkedAuto Update Statistics checkedNo other options should be checked on this dialog.


Configuring the Planning Database in SQL ServerConfiguring user and database settings3



Additional Configuration and Administration Issues

cha

pte

r

Additional Configuration and Administration IssuesBacking up the database4
Backing up the database
Business Objects recommends backing up the SRCIA 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 settingsThe following operating system settings are recommended for optimal performance with SQL Server and Business Objects Planning. These settings apply to Windows NT Server, Windows 2000 Server and Windows 2003 Server.

Performance and virtual memoryPerformance 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 ServerTo 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 Setting

Processor Scheduling Background Services


Additional Configuration and Administration IssuesRecommended operating system settings 4

Windows 2000 ServerTo 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:

Windows NT ServerTo configure the performance and virtual memory settings in Windows NT Server, go to Control Panel > System and select the Performance tab. Verify or change the following settings on this dialog:

Server memory accessThe server should be configured so that SQL Server has maximum access to the server’s memory.

Memory Usage System CacheVirtual Memory 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).

Option Setting

Option Setting

Optimize performance for Background ServicesVirtual Memory Click Change to view the virtual memory


Option Setting

Application Performance Set the Boost slider to None.Virtual Memory Click Change to view the virtual memory



Additional Configuration and Administration IssuesRecommended SQL Server configuration settings4
Windows 2003 Server and Windows 2000 Server
To configure the server memory access settings in 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.)

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).

Windows NT ServerTo configure the server memory access settings in Windows 2003 Server:1. Go to Control Panel > Network and select the Services tab.2. Click Network Services.3. Click the name of the server and then click Properties.4. 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 Business Objects 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 (7.0 / 2000) and select Properties.

2. On the Processor tab, verify or change the following settings:


Additional Configuration and Administration IssuesRecommended SQL Server configuration settings 4

SQL Server 7.0 and 2000

SQL Server 2005

3. For SQL 7.0 / 2000, click on the Memory tab, and verify that Dynamically configure SQL Server is selected.

Options Settings

Processor Make sure that all processors listed are checked for use.

Boost SQL Server priority on Windows

checked

Use all available processors checked

Options Settings

Automatically set processor affinity mask for all processors

checked

Automatically set I/O affinity mask for all processors checkedMaximum worker threads 0Boost SQL Server Priority checked


Additional Configuration and Administration IssuesRecommended SQL Server configuration settings4


SQL Server Administration Guide

Documents

Transcript of SQL Server Administration Guide