--- title: Data Provenance in Cognos Analytics description: Data provenance is something every Cognos administrator needs to be concerned about and that requires fully understanding the entire data chain from original source to end point consumption in reports, graphs, etc. image: https://www.envisn.com/hubfs/disparate-data-sources.jpg --- [![envisn](https://www.envisn.com/hs-fs/file-15282154-gif/images/logo.gif?width=120&name=logo.gif "envisn")](https://www.envisn.com) [![Request a Demo](https://hubspot-no-cache-na2-prod.s3.amazonaws.com/cta/default/70307/973f9256-ef61-4ab8-ab2d-a004a90a18be.png)](https://hubspot-cta-redirect-na2-prod.s3.amazonaws.com/cta/redirect/70307/973f9256-ef61-4ab8-ab2d-a004a90a18be) [![cognos security as youve never seen it - learn more about netvisn](https://www.envisn.com/hs/cta/cta/default/70307/3166c389-8135-4d84-9988-99dc8d523426.png)](https://www.envisn.com/hs/cta/cta/redirect/70307/3166c389-8135-4d84-9988-99dc8d523426) # Envisn's IBM Cognos Blog ## [Data Provenance in Cognos Analytics](https://www.envisn.com/envisn-cognos-blog/data-provenance-in-cognos-analytics) Posted by [The Envisn Team](https://www.envisn.com/envisn-cognos-blog/author/the-envisn-team) - [Tweet](https://twitter.com/share) ![external data sources in cognos](https://www.envisn.com/hs-fs/hubfs/disparate-data-sources.jpg?width=300&name=disparate-data-sources.jpg)*By Paul Hausser, [Envisn, Inc.](https://www.envisn.com/)* Most institutional data used for reporting purposes comes from one or more data warehouses which are typically aggregations of internal transaction systems like SAP, Oracle, etc. But more frequently today an equally large portion comes from external sources. This could be vendors/ suppliers, government sources, customers, etc. In fact, this segment of data is typically growing at a much faster rate than internal sources as companies need for this data becomes critical to just in time supply chain management as well as quality control. While use of external data sources has become essential across many industries it also poses challenges because the data may not have the same level of quality as that of internal data. And if there is a problem with a given data source, whether internal or external, is discovered it’s important to know immediately where and how it is being used. Beyond that there are other questions that may need to be addressed such as: - ***What data sources are being used across Cognos Analytics? *** - ***Are these data sources internal or external? *** - ***Where and how are they used within Cognos? *** - ***What data items from these data sources are being used? *** - ***Which objects in the Content Store are using data from a given database? *** - ***With what frequency is this data being viewed? And by whom? *** Little, if any, of this needed information is available within Cognos itself beyond which data sources are being used. For this you will likely need a third party solution to answer these questions. In this case here we are using the [**NetVisn**](https://www.envisn.com/netvisn) product to get data source and related information on actual usage within the Cognos environment. If a major problem with a data source is identified it can be important to immediately identify its impact and then take action to correct or isolate it. This requires both speed and precision for it to work successfully. ***Figure 1*** shows some of the data sources being used in a Cognos environment. The *SQLNORTHWIND.NORTHWIND.DBO* data source has been identified as having a problem with some of its data. The *ORDER DETAILS* table within this data source has incorrect data and needs to be replaced. ![report of data sources in cognos environment](https://www.envisn.com/hs-fs/hubfs/data-provenance-1.jpg?width=700&name=data-provenance-1.jpg) Our next step (***Figure 2***) is to do an analysis of *SQLNORTHWIND.NORTHWIND.DBO* data source and identify all of the objects in the Content Store that are using any of the data items from its *ORDER DETAILS* table. ![report of objects in cognos content store](https://www.envisn.com/hs-fs/hubfs/data-provenance-2.jpg?width=700&name=data-provenance-2.jpg) The results of our analysis are shown in ***Figure 3*** shows some of the total of 45 items found that are using data from the *ORDER DETAILS* table within this data source. ![cognos analysis results of objects from data source](https://www.envisn.com/hs-fs/hubfs/data-provenance-3.jpg?width=700&name=data-provenance-3.jpg) The final step would be to simply do a model item mass update replacing all of data items using that particular table with the new, corrected version from that data source. This step will also automatically validate the data lineage insuring that the report object will function correctly. What have we done here? We have identified a data source in the Cognos environment where there is a problem with a data source. We then did a dependency analysis to identify all objects that are currently using this data. This dependency analysis further identifies each data item within the data source and exactly where it is being used. Then it’s simply a matter of updating the FM model with the new, correct data source. Data provenance is something every Cognos administrator needs to be concerned about and that requires fully understanding the entire data chain from original source to end point consumption in reports, graphs, etc. Plus, it just makes sense to know your data’s provenance; where it came from and how it was created. *© Envisn, Inc. – 2019 – All Rights Reserved.  [Cognos Data Management ­](https://www.envisn.com/cognos-data-management)* *[![See what Envisn Tools can do for your Environment >](https://hubspot-no-cache-na2-prod.s3.amazonaws.com/cta/default/70307/68bf7ef9-0832-4510-8c14-2af0b7c692e9.png)](https://hubspot-cta-redirect-na2-prod.s3.amazonaws.com/cta/redirect/70307/68bf7ef9-0832-4510-8c14-2af0b7c692e9)*   Topics: [Cognos Analytics](https://www.envisn.com/envisn-cognos-blog/topic/cognos-analytics), [Cognos Data Provenance](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-provenance), [Cognos Data Sources](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-sources) *Your feedback is very important to us - we’d love to hear your comments!* ### Subscribe to Envisn's IBM Cognos Blog [![Your Content Store contains thousands of objects with hundreds of properties. netvisn gives you control of all of it learn more](https://hubspot-no-cache-na2-prod.s3.amazonaws.com/cta/default/70307/c76703b2-30ab-4086-9bc3-f2c890de7c5f.png)](https://hubspot-cta-redirect-na2-prod.s3.amazonaws.com/cta/redirect/70307/c76703b2-30ab-4086-9bc3-f2c890de7c5f) ### Posts by Category - [Cognos Content Store (22)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-content-store) - [Cognos BI Best Practices (21)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-bi-best-practices) - [Cognos Analytics (19)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-analytics) - [Cognos BI administration (19)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-bi-administration) - [Cognos Security (18)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-security) - [Cognos Tools (14)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-tools) - [Cognos Audit Data (11)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-audit-data) - [Cognos Reporting (9)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-reporting) - [Cognos Auditing (8)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-auditing) - [Cognos 10 (7)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-10) - [Cognos Framework Manager (7)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-framework-manager) - [Cognos Metadata (7)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-metadata) - [BI Trends (6)](https://www.envisn.com/envisn-cognos-blog/topic/bi-trends) - [IBM Information on Demand (6)](https://www.envisn.com/envisn-cognos-blog/topic/ibm-information-on-demand) - [Cognos Audit Log (5)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-audit-log) - [cognos impact analysis (4)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-impact-analysis) - [Big Data (3)](https://www.envisn.com/envisn-cognos-blog/topic/big-data) - [Cognos Data Sources (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-sources) - [Cognos Documentation (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-documentation) - [Cognos Scheduling (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-scheduling) - [Product Information (3)](https://www.envisn.com/envisn-cognos-blog/topic/product-information) - [cognos data lineage (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-lineage) - [Archiving Cognos Content (2)](https://www.envisn.com/envisn-cognos-blog/topic/archiving-cognos-content) - [Cognos FM Model (2)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-fm-model) - [Cognos migration (2)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-migration) - [Announcements (1)](https://www.envisn.com/envisn-cognos-blog/topic/announcements) - [Cognos Change Management (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-change-management) - [Cognos Data Provenance (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-provenance) - [Cognos Hotfiles (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-hotfiles) - [Cognos Powerplay (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-powerplay) - [Cognos Triggers (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-triggers) - [Consolidating Cognos Environments (1)](https://www.envisn.com/envisn-cognos-blog/topic/consolidating-cognos-environments) - [Impromptu (1)](https://www.envisn.com/envisn-cognos-blog/topic/impromptu) - [Merging Content Stores (1)](https://www.envisn.com/envisn-cognos-blog/topic/merging-content-stores) - [Remote Cognos Management (1)](https://www.envisn.com/envisn-cognos-blog/topic/remote-cognos-management) - [cognos deployments (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-deployments) - [cognos fm model documentation (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-fm-model-documentation) - [cognos workspace (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-workspace) - [netvisn (1)](https://www.envisn.com/envisn-cognos-blog/topic/netvisn) [see all](https://www.envisn.com/envisn-cognos-blog/data-provenance-in-cognos-analytics#) ### Posts by Popularity [![free download expert guide to cognos audit data](https://www.envisn.com/hs/cta/cta/default/70307/6933ba0f-4664-4d5d-9413-edf64d7b2644.png)](https://www.envisn.com/hs/cta/cta/redirect/70307/6933ba0f-4664-4d5d-9413-edf64d7b2644) ### [Cognos Tools from Envisn](https://www.envisn.com/envisn-products) [NetVisn](https://www.envisn.com/netvisn) [AutoVisn](https://www.envisn.com/autovisn-cogos-scheduler) [UniVisn](https://www.envisn.com/univisn-cognos-performance-management) [DocuVisn](https://www.envisn.com/docuvisn-cognos-documentation) ### [Cognos Resources](https://www.envisn.com/resources) [Envisn’s IBM Cognos Blog](https://www.envisn.com/envisn-cognos-blog) [Custom Query Library](https://www.envisn.com/custom-query-library) [Tutorial Videos](https://www.envisn.com/cognos-demo-videos) [Mastering Cognos Security](https://www.envisn.com/mastering-ibm-cognos-security) [Content Store Survival Guide](https://www.envisn.com/content-store-survival-guide) [Expert Guide to Cognos Audit Data](https://www.envisn.com/cognos-audit-data-expert-guide) ### [Contact Envisn](https://www.envisn.com/contact) [Request a Demo](https://www.envisn.com/request-a-demo) [Support](https://www.envisn.com/support) 512-991-3999 [info@envisn.com](mailto:info@envisn.com) ### Latest Cognos Posts | [![youtube](https://www.envisn.com/hs-fs/hubfs/youtube.png?width=30&name=youtube.png)](https://www.youtube.com/user/envisn) | [![linkedin](https://www.envisn.com/hs-fs/hubfs/linkedin.png?width=30&name=linkedin.png)](https://www.linkedin.com/company/envisn-inc./) | [![twitter](https://www.envisn.com/hs-fs/hubfs/twitter.png?width=30&name=twitter.png)](https://twitter.com/Envisn) | [![facebook](https://www.envisn.com/hs-fs/hubfs/facebook.png?width=30&name=facebook.png)](https://www.facebook.com/envisn/) | | --- | --- | --- | --- | [![Real Time Analytics](https://static.getclicky.com/media/links/badge.gif)](http://clicky.com/101126274) ![Clicky](https://in.getclicky.com/101126274ns.gif) 3000 Polar Lane, Suite 901, Cedar Park, TX 78613 USA *Serving North America, Europe, and the UK with plans to expand to other areas in the near future. **[Privacy, Copyright & Liability](https://www.envisn.com/privacy-copyright-liability)*