Académique Documents
Professionnel Documents
Culture Documents
Planning
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.
Third-party Business Objects products in this release may contain redistributions of software licensed from third-party contributors.
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
Introduction
SQL Server Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Technical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
SQL Server User Interface Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
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.
Intended Audience
Installation, 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 Requirements
The 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.
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.
This chapter details the required SQL Server installation parameters for Business Objects
Planning. Business Objects Planning can also be used with an existing installation of SQL
Server, if the existing installation meets certain requirements.
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.
.
Services Accounts / Service Choose Use a Domain User account (this set-
Settings ting is preferred, but not required).
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:
z Create the srcadmin login user.
z Create the database transfer and backup devices.
z Restore the Business Objects Planning database.
z 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 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
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.
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.
Option Setting
Name srcadmin
Database master
Language <Default>
3. On the Server Roles tab, make sure that no permissions are selected.
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:
z In SQL Server 2005, open the Server Objects folder, right-click Backup
Devices and select New Backup Device.
z In SQL Server 7.0 / 2000, open the Management folder, right-click Backup and
select New Backup Device.
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
Option Setting
To database SRCIA
Restore checked
Option Setting
Restore as:*
SRCIA D:\SQLData\SRCIA.mdf
SRCIA_Log C:\SQLLog\SRCIA.ldf
* 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.
1. Right-click on the Databases folder, select All Tasks and then select Restore
Database.
Option Setting
Backup number 1
Option Setting
SRCIA_Data D:\SQLData\SRCIA.mdf
SRCIA_Log C:\SQLLog\SRCIA_Log.ldf
* Although the logical file names cannot be changed, you can edit the
physical path to place the files in different locations. 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.
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:
z On the Server Roles tab, verify that no server roles are checked for database
SRCIA.
z 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.
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:
z In SQL Server 2005: map for the SRCIA database and with dbo as the
assigned user and default schema.
z In SQL Server 7.0 /2000: permit for the SRCIA database and with dbo as the
assigned user.
Database Options
The 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.
Option Setting
Option Setting
Option Setting
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.
Important: 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).
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
Option Setting
Windows NT Server
To 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:
Option Setting
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).
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).
Options Settings
Options Settings
3. For SQL 7.0 / 2000, click on the Memory tab, and verify that Dynamically
configure SQL Server is selected.