Siebel CRM Desktop for Microsoft Outlook Administration Guide > Administering Siebel CRM Desktop > Controlling How Siebel CRM Desktop Handles CRM Data >

Storing Objects in a Database to Improve Performance

To improve performance, you configure Siebel CRM Desktop to store the child objects, seed data, lookup values, intersection records, and so on outside of the PST and OST files that Outlook typically uses for storage. CRM Desktop can store these items in an external database. To do this, you move these objects from the siebel_basic_mapping.xml file to the following tag:

database

To store objects in a database to improve performance

1. Use an XML editor to open the siebel_basic_mapping.xml file.
2. Add the database tag immediately following the existing sd2_meta tag:

   <sd2_meta>
     <database>
   ...
   </database>

3. Move the existing objects inside the region.

   For example:

   <type id="Employee" icon="type_image:Employee:16">
     <field id ="Primary Organization Id">
       <type>
         <simple type="foreign_key"/>
       </type>
     </field>
     <field id ="Primary Position Id">
       <type>
         <simple type="foreign_key"/>
       </type>
     </field>
     <field id ="First Name">
       <type>
         <simple type="string"/>
       </type>
     </field>
     ...
   </type>

   You must not move some objects. For more information, see Objects That You Must Not Store in a Database.

You must specify the following items in the type tag:

• type id. The name of the type.
• icon. The image from the resource that CRM Desktop must use for this type.

To define the field, you must specify the field Id of the field and the field type. CRM Desktop supports the following types:

• string
• integer
• double
• datetime
• boolean
• binary
• foreing_key (for ID fields).

Objects That You Must Not Store in a Database

The following objects must remain in the types tag. You must not move them:

• All built-in objects and their CRM Desktop equivalents, such as Contact, Email, task, Calendar, and so on
• All custom parent objects that CRM Desktop displays in the tree structure, such as Account or Opportunity
• The Action object, which serves as a proxy for Calendar, task, and Email items
• The Attachment object, which requires special handling and cannot be moved