Siebel Business Analytics Server Administration Guide > Creating and Administering the Physical Layer in a Repository >

Process of Creating the Physical Layer from Relational Data Sources

Importing the physical schema saves you time and effort by importing the structure for the physical layer. You can import schema for supported data sources. If you do not import the schema, you must create each table, primary key, foreign key, and any other objects against which you want to generate queries. Data from these sources can be displayed on Oracle's Siebel Intelligence Dashboards.

The following is a list of tips to help you when importing a physical schema:

• When you import schema for most databases, the default is to import tables, primary keys, and foreign keys.

  NOTE:  It is recommended that you not import foreign keys from a database because the process is lengthy when importing a large number of tables.

• When you import physical tables, be careful to limit the import to only those tables that contain data that are likely to be used in the business models you create. You can use a filter (table mask) to limit the number of tables that appear in the import list. This makes it easier to locate and select the tables that you want to import.
• You can also import database views, aliases, synonyms, and system tables. Import these objects only if you want the Analytics Server to generate queries against them.
• Importing large numbers of extraneous tables and other objects adds unnecessary complexity and increases the size of the repository.

To create the physical layer by importing the schema, complete the following tasks in the sequence shown:

• Importing a Physical Schema from Relational Data Sources
• Setting Up Database Objects
• Setting Up Connection Pools
• About Physical Tables
• Creating and Setting Up Physical Tables