Upgrade Guide for Microsoft Windows > Preupgrade Tasks > Verifying Database Server Configuration >

Microsoft SQL Server Database Server Configuration


This section contains guidelines for obtaining optimal performance from the Microsoft SQL Server database for use with Siebel eBusiness Applications.

These settings should be used only as guidelines for your upgrade configuration. Your final settings may vary based on the server hardware configuration, the number of users, and the type of workload.

Additional information on the configuration of Microsoft SQL Server is available in the Microsoft documentation, information provided by your hardware vendor, and other sources. For additional information concerning tuning options for Microsoft SQL Server, refer to the Microsoft documentation.

CAUTION:  Never make changes to your Siebel database schema unless instructed on how to do so for a specific purpose by Siebel eBusiness Applications documentation. Otherwise, you may corrupt your entire system and thereby render it unsupportable.

If you are upgrading from Siebel eBusiness Applications Release 6.x, you must upgrade the Microsoft SQL Server database from 7.0 to SQL Server 2000, using Microsoft's documentation and tools. After you have upgraded SQL Server, be sure that you configure it according to the following recommendations before proceeding with the upgrade.

NOTE:  The development database must use binary sort order. Likewise, binary sort order is recommended for production databases for performance reasons. Binary sort order is not the default sort order for Microsoft SQL.

Temporary Database Space

This is the database that Microsoft SQL Server uses for temporary space needed during execution of various queries.

Configuration Parameters

Table 10 describes Microsoft SQL Server database configuration parameters that must be set for the upgrade. Before upgrading a MS SQL Server database, make sure that your database server meets these parameters. For parameters not listed in this table, Siebel Systems recommends that you accept the default settings.

Table 10.  Microsoft SQL Configuration Parameters
Parameter
Setting/Comment
Max. degree of parallelism
0
Cost threshold for parallelism
5
Fill factor (%)
90
Index create memory (KB)
0

NOTE:  Most of these parameters do not differ from the default settings.

Siebel Database Options

Set the following Siebel database options to ON (enabled) for the upgrade. After your upgrade is complete, you must reset these options to their installation settings, as described in Postupgrade Tasks.

truncate log on chkpt. This option should be set to ON (enabled) for upgrade only. Also, for upgrade only, execute the alter database command against Siebel database, specifying set recovery simple.

NOTE:  You must revert to the original database recovery setting after the upgrade.

torn page detection. Set this option to ON (enabled).

auto create statistics. Set this option to ON (enabled).

auto update statistics. Set this option to ON (enabled).

Rebuilding Clustered Indexes

If you have large tables that you use extensively (such as S_EVT_ACT, S_CONTACT, S_OPTY, S_OPTY_POSTN, S_ORG_EXT), use the MS SQL Server create index command with drop_existing clause to rebuild large tables with high fillfactor (60%-70%).

Updating Statistics

The cost-based optimizer in Microsoft SQL Server uses statistics about tables and indexes to compute the most efficient access plans. When statistics become inaccurate, which can happen for tables with high insertion rates, high deletion rates, or both, and for associated indexes, the performance of database operations can degrade dramatically.

To update statistics, run sp_updatestats to refresh statistical information in the Siebel database.

Increasing Database File Size

If your RDBMS is MS SQL Server, you should increase your database file size by resetting the Autogrowth parameter to between 25% and 50%. Failure to do this could diminish upgrade performance and possibly impact the success of your upgrade.


 Upgrade Guide for Microsoft Windows
 Published: 20 October 2003