In this chapter, we learned to understand the object types that define the data layer in the Siebel Repository, namely tables, columns, indexes, and user keys. In addition, we discussed the implications of changes to the physical schema and that it is beneficial to use alternative solutions such as preconfigured extension tables instead of creating custom tables or columns.

Of course, company requirements will exist which that physical schema changes necessary. In this chapter, we also learned how to create new columns, tables, and indexes and synchronize the Siebel Repository metadata with the physical schema of the relational database.

In the next chapter, we will expand on the topic of 1:M extension tables and learn how to create the necessary business layer objects to support new child entities.