Typical Storage screen for an Oracle table:
Location
Fields | Description |
|---|---|
Target Location | The target location object that defines the path of the table. Select (local) for a local table or select the target schema if you are locating tables in different schemas. Note The Force Target Usage setting in the Tools > Options > Storage > Target Usage removes the local target option from the drop-down list. Refer to Target Usage for details.
|
Database Type | The database type for a connection that is used for target DataWarehouse tables. |
Schema | The schema where the table is located, if applicable. |
Create DDL Template | Optional. Specify the template to use when creating a new DDL procedure script. This option is only visible if a DDL template is available for this database type. Default value is None. |
Storage
Note
When upgrading from a RED version previous to 6.8.2.0 and moving existing objects to a target location, all procedures that reference those objects need to be rebuilt. Any FROM clauses also need to be manually regenerated in order for the table references to be updated to the new [TABLEOWNER] form.
Warning
If the database type does not support moving tables, such as Oracle, Greenplum, Netezza, Teradata and PDW, all affected tables also need to be manually recreated after any storage changes. Please note that changing the Storage for Dimension and Fact tables need to be handled very carefully, as artificial key relationships between Dimension and Fact could become out of sync. Recreating Fact tables and large Dimension tables might take a considerable amount of time.
Fields | Description |
|---|---|
Tablespace | Select a name from the drop-down list box. If no tablespace is selected in Oracle, then the default tablespace for the schema is used. |
Initial extent (KB) | The size of the first extent of a created database table. The default is 0 kilobytes - use the tablespace's default value. For locally managed tablespaces, this field is ignored. |
Next extent (KB) | The size of the next (second) extent of a created database table, unless percent increase is specified. The default is 0 kilobytes - use the tablespace's default value. For locally managed tablespaces, this field is ignored. |
Minimum extents | The number of extents the table is created with. The default is 0 - use the tablespace's default value. For locally managed tablespaces, this field is ignored. |
Maximum extents | The maximum number of extents the table can have. The default is 0 - use the tablespace's default value. For locally managed tablespaces, this field is ignored. |
Percent increase | The size the next extent is as a percent of the previous extent added. For example, a value of 5 will create the next extent 5% bigger than the previous extent added. The default is 0 - use the tablespace's default value. For locally managed tablespaces, this field is ignored. |
Percent free | The amount of free space to leave in each extent in Oracle. The default is 0 - use the database default. |
Other
Fields | Description |
|---|---|
Optional CREATE Clause | Database-specific-and-compliant DDL to append to the generated CREATE TABLE statement, such as a logging clause and/or a partition clause.
Tip To edit Oracle's default values for new objects, go to the Tools > Options menu - Default Optional CREATE Clause. |
Buffer Pool | Oracle Dimension tables only: Mark the table to be retained in a special buffer pool. Possible values are Default, Keep, Recycle and not set (blank). The default is not set. |
Dimension Tables:
Fields | Description |
|---|---|
Artificial Key Sequence Name | Name of the database sequence associated with the specific object. Enter the required new sequence name when creating a new table. The default key value for Dimensions is dim_tablename_seq. Specific Artificial Key Sequence Names can also be added to Data Store and EDW 3NF tables when an artificial key column is added to the table. Warning When altering the Artificial Key Sequence Name for existing tables, ensure the START WITH option is configured properly to avoid unique constraint violations. |
Artificial Key Sequence Attributes | This option allows adding database specific and compliant options to the generated create sequence statement such as START WITH, INCREMENT BY or CACHE. |