Home > ETL Best Practices > Best Practices for Data Warehouse Database Developers – metadata and ETL

Best Practices for Data Warehouse Database Developers – metadata and ETL

There is an older article on Best Practices for Data Warehouse Database Developers. I find it still relevant.

The article addresses many of the challenges in developing an ETL process. What interests me is the the importance of metadata to ETL the article emphasizes. I understand that the metadata is arguably one of the cornerstones of data warehousing, and the design and of the ETL subsystem is critical to a data warehouse or an ODS system, but I never really associated metadata with ETL. This is probably because the word metadata is not precisely defined in my mind, despite its widespread use in the industry.

The article discussed a few meta data that are important to ETL.

1. A usable data dictionary before starting heavy-duty development

2. Query plans, run times and performance benchmarks; save them in the database

3. ETL, validation and processing errors; save them in shared database tables

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: