Siebel Analytics Server Administration Guide > Working in a Repository's Physical Layer > Physical Layer Objects >

Using the Physical Table Dialog Box


In the Physical Table dialog box you can define general properties, columns, a primary key, and foreign keys. If the table definitions are imported together with their columns and key information, the properties are configured automatically (assuming that the keys are defined in the database).

You can use the Physical Table dialog box to perform the following tasks:

Creating or Editing a Physical Table

Use the General tab of the Physical Table dialog box to create or edit a physical table in the Physical layer of the Administration Tool.

To create a physical table or edit general properties for the table

  1. In the Physical layer of the Administration Tool, do one of the following:
  2. Enter a name for the table.
  3. The name of the table and its associated path are displayed in the Object Name field. When XML data is being used as a data source, this field displays the fully qualified name of a table used in an XML document.

  4. Click the Permissions button to open the Permissions dialog box, where you can assign user or group permissions to the table.
  5. For information about assigning permissions to a physical table, see Setting Permissions for Repository Objects.

    TIP:  You should not set permissions on physical layer objects except for connection pools. You should set permissions on presentation layer objects.

  6. To include the table in the Siebel Analytics Server query cache:
    1. Select the option Make table cacheable.
    2. This causes the Cache persistence time settings to become active. These settings specify how long the entries for this table should persist in the query cache. This is useful for OLTP data sources and other data sources that are updated frequently. In general, you should check this option for most tables.

    3. To specify in minutes or seconds how long the entries should persist, select (minutes) or (seconds) from the drop-down list on the right, and type a whole number into the field on the left.
    4. The default value is Infinite, which means that cache entries do not automatically expire. This does not mean that an entry will always remain in the cache. Other invalidation techniques, such as manual purging, LRU (Least Recently Used) replacement, metadata changes, and use of the cache polling table, still result in entries being removed from the cache.

      For information about the cache polling table, see Troubleshooting Problems with an Event Polling Table.

      NOTE:  If a query references multiple physical tables with different persistence times, the cache entry for the query will exist for the shortest persistence time set for any of the tables referenced in the query. This makes sure that no subsequent query gets a cache hit from an expired cache entry.

  7. Select an Object Type from the drop-down list, and, if necessary, enter the appropriate text in the text pane.
  8. See Table 12 for a description of the available object types.

  9. (Optional) If you selected an object type of None or Alias, you can enter a database hint.
  10. For information about database hints, see Using Database Hints.

  11. (Optional) Type a description of the table.

Using the Columns, Keys, and Foreign Keys Tabs

The Columns, Keys, and Foreign Keys tabs in the Physical Table dialog box allow you to view the columns, keys, and foreign keys, respectively, that are associated with the table.

These are the buttons that appear in the tabs:

Setting Properties for an XML Data Source

Use the XML tab to set or edit properties for an XML data source. The XML tab of the Physical Table dialog box provides the same functionality as the XML tab of the Connection Pool dialog box. However, the properties you set in the Physical Table dialog box override the corresponding settings in the Connection Pool dialog box. For instructions on setting properties in this tab, see Setting Properties for an XML Data Source.


 Siebel Analytics Server Administration Guide 
 Published: 23 June 2003