Home > ETL Best Practices > ETL Process Design – Naming Convention

ETL Process Design – Naming Convention

I found myself modify my naming convention quite often because I am not happy with them in the first few rounds of the design process. After a while, I kind of settled with the following set of rules.

1) Prefix for different objects. This is not unique for ETL process design. But it’s very important for any SQL development work. Typically, I use the following:

tbl: for all table objects
  • tblStandardPCMakeModel
  • tblTranslate
  • tblMarimbaMachine
usp: for all procedures
  • usp_PopulatePCAssetMarimba
  • usp_StandardizeMfg
  • usp_LoadRawDataMarimba
vw: for all views
  • vwPCAsset
  • vwSoftwareAsset
etl: for all SSIS packages
  • etlEAM_LoadRawData
job: for all SQL agent jobs
  • jobEAM_LoadRawData
ix: for all indexes
  • ix_Ast_lAstId

2) Reserve a few verbs, nouns, and adjectives for the project. This is not unique for ETL process design either. But for any ETL development work, using the meaningful verbs, nouns, and adjectives is the foundation for a good design and also a good start for your design documentation (if anybody asks for that).

Here are some of the words I reserve for the project.

image

Categories: ETL Best Practices
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: