Bookshelf Home | Contents | Index | Search | PDF

Siebel Assignment Manager Administration Guide > Running Assignment Manager > Running Assignment Manager in Batch Mode >

Assignment Manager Performance in Batch Mode

---

If users experience slow response time while running Assignment Manager in batch mode, review the settings on virus software installed on the applicable server. Implement one or more of the following settings to improve batch assignment performance.

Virus scan only program files.
Exclude all outbound files from virus scanning.
Exclude the RDBMS directory where all msb files are located from virus scanning.

Make sure to run a full virus scan on all files during the weekend or off-peak time if the preceding settings were used.

You can also implement one or more of the following to boost batch performance in batch mode:

Increase the BatchSize parameter, for example, set the batch size to 500 (the default is set to 100).

This increases the number of records that are processed within a transaction before a commit occurs, resulting in less resources used and faster assignment.

NOTE:  Only set large batch sizes when there are no or very few users on the system.

Create multiple instances of Batch Assignment (using WHERE clause statements). See Running Multiple Instances of Assignment Manager in Batch Mode.
Select a good filter.

This reduces the time it takes to retrieve Object records.

NOTE:  Use indexed field or fields for comparison in the object WHERE clause, such as Name for Account and Opportunity, or Last Name for Contacts.

Use better logic.

For example, if you want to run Account Assignment based on account name, you can create multiple batches so that the first batch starts with names beginning with the letter C through K, the second batch starts with the letter L through R, and so on.

Consider the following logic:

Object Where Clause: WHERE NAME > `B' AND NAME < `L'

Although this causes the database to retrieve account records with names starting with the letter C through K, the WHERE clause is specified in such a manner that if accounts starting with the letter M through Z are encountered, they are passed on the first round because the values are > B. They are then eliminated in the second round (< `L') by the database. These records are not needed in the batch because there is a cap of account names less than L.

It is better logic to use:

Object Where Clause: WHERE NAME < `L' AND NAME >`B'

By switching the order of the conditions, the extra parsing required by the database in the second round is eliminated because most of the names start with a letter greater than B.

Bookshelf Home | Contents | Index | Search | PDF