DATA_HUB Tables and Views
Anchor |
---|
| DATA_HUB Tables and Views |
---|
| DATA_HUB Tables and Views |
---|
|
DATA_HUB tables should begin with HUB. DATA_HUB views created under MARTIAN should end with "_V".
Back to Top
Detail Tables
Anchor |
---|
| Detail Tables |
---|
| Detail Tables |
---|
|
A detail table should end with DETAIL.
- Examples: CRSE_SECT_DETAIL, GRDE_DETAIL
Back to Top
GOFAST Tables
Anchor |
---|
| GOFAST Tables |
---|
| GOFAST Tables |
---|
|
GOFAST tables should begin with GOFAST.
Back to Top
Grade Tables
Grade tables should begin with GRDE.
Back to Top
ID Request Tables
Anchor |
---|
| ID Request Tables |
---|
| ID Request Tables |
---|
|
Data Warehouse ID request tables should begin with IDR.
Back to Top
OASIS Financial Information Tables (OFI)
OASIS financial information tables should begin with OFI.
Back to Top
ODS Table (temporary table, control table)
An ODS table is a table used to hold data during a data extract/load process and that will not be made available to users should have a name that begins with ODS_ (Optional Data Store). ODS tables are often referred to as temporary tables, even though, some tables contain data that is not truncated after use. Data in a table, such as a control table, may be updated or appended via an automated process or manually input. Control table names should also begin with ODS_. If data in a control table needs to be made available to users, create a view of the ODS table using the table name minus ODS_.
- Examples: ;ODS_GOFAST_GRANT_BUDGET_TREE, ODS_GOFAST_DL_CTRL
Back to Top
Registration Tables
Anchor |
---|
| Registration Tables |
---|
| Registration Tables |
---|
|
Tables containing OASIS registration information should begin with REG. Tables containing student registration information should begin with REG_STDN.
- Examples: REG_TRANS_SUM, REG_STDN_CRN_HIST
Back to Top
Snapshot Tables and Materialized Views
Anchor |
---|
| Snapshot Tables and Materialized Views |
---|
| Snapshot Tables and Materialized Views |
---|
|
A snapshot tables and materialized views should have the same name as the table in the production system, and it should be prefixed with the system name.
- Examples: FAST_PS_FUND_TBL, OASIS_SPRIDEN_USF_ID, GEMS_PS_ACCT_CD_TBL
Back to Top
Summary Table
Anchor |
---|
| Summary Table |
---|
| Summary Table |
---|
|
A summary table name should end with _SUM or SUMMARY.
- Examples: REG_CS_SCH_SUM, AWS_COURSE_SECTION_SUMMARY
Back to Top
Table/View Groupings
Anchor |
---|
| Table/View Groupings |
---|
| Table/View Groupings |
---|
|
Tables/views sharing a close association should have names that group them together.
- Examples: GOFAST_DL_BS, GOFAST_DL_REVEXP, and HUB_ADM_EXCEPTIONS_CURR, HUB_ADM_EXCEPTIONS_HIST
Back to Top
Table/View Name Length
Anchor |
---|
| Table/View Name Length |
---|
| Table/View Name Length |
---|
|
If the table/view will be assigned a DAL, the length of the name cannot be longer than 27 characters or the nightly DAL view create process will fail.
Back to Top