Lineage for RDBMS “Views”

Hi Everyone…

Someone asked me yesterday about being able to perform lineage in Metadata Workbench on a database “View”. It dawned on me that I may have never created a post on this very important subject. Formal Database views, as created in the rdbms catalog via a CREATE VIEW sql statement, are fully supported for Data Lineage purposes by Information Server and the Metadata Workbench.

The key is in the method of import.

When you import your rdbms catalog information via Connector (in 8.7 Metadata Asset Manager, or in any 8.x release via DataStage, Information Analyzer, or FastTrack), the views are imported and get their own icon for display purposes within the “Hosts” tree (or Implemented Data Resources if you are in 8.7). The details of the view are available for display, and will show the SQL used in the CREATE VIEW statement to originally create it.

More importantly, when you perform “Automated Services” (a.k.a. “stitching”, or in 8.7, “Detect Associations”), Metadata Workbench will parse thru the SQL of the CREATE VIEW and establish data lineage connections to the “source tables” of the view! Once this is done, you will have lineage for the view back to its source tables, and of course, anything that is upstream from those tables, or downstream from the view itself!

Ernie

Advertisements

One Response to “Lineage for RDBMS “Views””

  1. Kunal Johar Says:

    Hi Ernie, I stumbled upon your post trying to figure out how to generate lineage using View and if there is some functionality in metadata workbench to parse the SQL in View. We have InfoSphere 8.7 with only Metadata workbench and Business Glossary, no datastage. We use IDA to reverse engineer databse models and import them into metadata workbench using IMAM which brings in Database Views with the SQL. The method you described above would work if we have datastage along with metadata workbench. Since we do not, I cannot run detect associations because there is no transformation project.
    Is there some way I can still utilize the functionality of “Automated Services” in metadata workbench to parse the Views and generate lineage back to the source table.
    Thank you
    Kunal


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: