You are on page 1of 2

Catalog contains tables, views , tables and so on.

All these objects are organized into schemas


and schemas are used to categorize the database contents according to customer defined
groupings
The column view that you create are always located under schema _SIS_BIC and their metadata
in schema _SIS_BI.
SQL processor handles DML statements (INSERT,DELETE,MODIFY) and other DDL statements for
tables, views, columns are dispatched to metadata manager
Data Provisioning

Referntial Join:

It is semantically an inner join that assume that referential integrity is given which means that the left
table always have a corresponding entry on the RIGHT table. It can be seen as an optimized or faster
inner join where the RIGHT table is not checked if no field from the RIGHT table is requested. That
means that the Referential Joins will be only executed, when fields from both tables are requested.
Therefore, if a field is selected from the RIGHT table it will act similar to inner join, and if no fields from
the RIGHT table is selected it will act similar to a left outer join. From performance perspective, the Left
Outer Join are almost equally fast as Referential Join, while the Inner Join is usually slower due to the
fact, that the join is always executed.
Analytic View: Helps you create fact table by adding and joining the tables in data foundation node.
Additionally, tables added in data foundation can be joined with attribute views in logical join

Logical Join : displays only fields you have chosen to include in output of data foundation
node, as well restricted and calculated columns can be define.

Data foundation : view shows physicals tables with all the fields that can be incorporated in final
model

You might also like