Columns

Best Practices for Columns

The following best practices apply to columns:

■ Always use all upper case characters for table names.

■ Make sure you set the Table Type property correctly in the Tables tab of the Design

view.

■ Always use all upper case characters for column names.

■ If you have a foreign key column, associate the foreign key table with the join

column. DAC uses this information to identify all the related tables to be loaded

when a certain table needs to be loaded in the data warehouse.

■ For Teradata databases:

– Pay attention to which columns need to gather statistics. Note that column

statistics are somewhat equivalent to indexes.

– If you would have had indexes that span multiple columns for other

databases, consider defining multi-column statistics for Teradata.

– Pay attention to the Teradata Primary Index property.

■ Do not register any columns for source system container tables.

■ Make sure you add all the appropriate system columns. For example, all tables

should have the following:

– ROW_WID in number format.

– INTEGRATION_ID in varchar format.

– DATASOURCE_NUM_ID in number format.

– ETL_PROC_WID in number format.