staging tables naming convention is: /LT1/DS
Tips for Using ETL Staging Tables.
Table names must follow the rules for SQL Server identifiers, and be less than 128 characters.
My advice is to pick a naming convention and adhere to it. What is the best practice to name the tables in this scenario? 1 - Introduction. I don't know that there is really any "best" naming convention out there, as it really boils down to personal preference and ease of development. There should be some logical, if not physical, separation between the durable tables and those used for ETL staging. SQL naming conventions for tables, and all the associated objects such as indexes, constraints, keys and triggers, are important for teamwork. If you wish to separate words with an underscore, do so in all of your database objects. This resemblance allows staging tables to also be used as interface tables between the transactional database sources and data warehouse target tables. The staging table structure is independent of source data structures and resembles the structure of data warehouse tables.
When you do decide to use staging tables in ETL processes, here are a few considerations to keep in mind: Separate the ETL staging tables from the durable tables. If you wish to use camelCase, do so in all of your database objects. When you export a project from DEV to QAS – first the staging table names are imported from DEV – then you need to do a synchronisation (system displays automatically this hint) -> new staging tables are beeing generated with naming convention above.
The staging tables for the Usage Accelerator are tagged as WS_
Data Warehouse: Naming convention techniques The naming convention is a key component of any IT project. We would like to differentiate these staging tables and report tables using naming convention. The purpose of this article is to suggest a standard for a practical and effective Data Warehouse design. Using Prefix or Suffix?