Impact Analysis¶
Find every universe, report and user affected before a database table or column is changed or dropped, so the change goes ahead without breaking reports.
Goal¶
A DBA plans to drop table INVOICE_001. Without impact analysis, report developers must ask around for days, the table stays, and unused database objects keep confusing data modelers. With MetaMiner you answer "who uses this table?" in minutes, from metadata MetaMiner has already collected.
Impact analysis means identifying which reports, universes, formulas, variables, users and groups are affected when a reusable part of the system, such as a database table, changes or disappears.
Who¶
BI administrators and report developers, working with the DBA who owns the change.
Before you begin¶
- MetaMiner collects universe, Web Intelligence and Crystal Reports detail for the environment. See Document Processing.
- You have the MMC permission Tab: Impact Analysis DB. See Permissions Reference.
- For usage figures (who opened the reports), MetaMiner collects audit data. See Audit and CMS Databases.
What MetaMiner traces¶
| Content | Traced to the database through |
|---|---|
| Universes (UNV, UNX) | Tables, columns and joins of the universe |
| Web Intelligence documents | Universe objects in each data provider, free-hand SQL and the generated data provider SQL |
| Crystal Reports | Tables and fields, command text (custom SQL) and Business Views |
TODO: confirm impact coverage for other content types
Confirm whether Analysis for Office, Lumira and Design Studio content appears in database impact results, and through which source types (BEx query, SAP HANA, Excel/CSV).
Steps¶
Find what uses the table¶
- In the MMC, open the Impact Analysis - DB tab. See Database Impact.
- Find the database, schema and table (or column) with the filter or search.
- Right-click the table and choose View Impacted Documents.
- Review the result: each universe and document that uses the table, with its folder.
- Export the list from the result window and send it to the DBA and report owners.
Image of the Impacted Database Objects window listing universes and documents for one table here
../images/use-cases/impact-db-impacted-documents.png
Check the universe side¶
- In the CMS Explorer, right-click an affected universe and choose Impact Analysis.
- Review which objects use the table and which documents use those objects.
Decide with usage data¶
- Open MM-W10 Object Use Overview or MM-D01 Activity and Data Source for the affected universes to see document activity.
- Or run IK-018 (UNX) or IK-019 (UNV) from the SQL Script Catalog in Meta Query.
- In the Web Console, the Blast Radius dashboard gives the same answer in a browser.
Expected result¶
A list of every universe object, Web Intelligence document and Crystal Report that depends on the table, with owners and recent usage. The DBA can drop unused tables and schedule changes for used ones with the report owners.
Variations¶
- Column rename: search the data provider SQL for the column name with MM-W17 Data Provider SQL, and Crystal command text with MM-C17 Command Text Use.
- Whole database move: follow Repoint Reports to a New Database.
- Universe object change, not a table change: use MM-W11 Object Use per Object and Unused Universe Objects.