How to save profiling result as view for multiple table(50+ tables)

Karthik_Anbusekar
edited June 27 in General

I have many tables, i need to run profiling on each of the tables and need to save the results as view. Since i have more number of tables, is there any way to do this altogether, rather then doing the same thing each table one by one.

Best Answers

  • James T Sidebotham
    James T Sidebotham Contributor
    Answer ✓

    I've also done that for 50+ tables. Just put headphones on, and it'll be done in an hour.

  • Hi Josh Boxer,

    Thanks for the information.

    I am planning to put those all tables (50+) in single dashboard. So that user can able to access profiling results of each table and acts accordingly.

    If this is not a good way to present profiling results to user, Kindly suggest some better way to do this.

  • James T Sidebotham
    James T Sidebotham Contributor
    Answer ✓

    An approach that I have taken is to send the single dataset to Azure Blob storage. From there it gets picked up by a Power BI report and presented through SharePoint. The report is filtered by table name, which the user just uses a drop down. I do that for all validation results too. Easy way for the different business groups to see the state of the data in a single report / dashboard.

Answers

  • What I have done in the past is during profiling, save the results to a multi-batch dataset. Include the metadata when you do the profiling, so that you get the dataset name. Then when you have profiled your 50 tables, you have one master Profile dataset. From there you can create views as you wish. If you are wondering if you could automate profiling for a list of source datasets - I am not aware, but maybe the Aperture staff know a trick?

  • Karthik_Anbusekar
    edited June 28

    Thanks sidebotham,
    But i need the profiling results of each table as separate view. So that i can use them in Dashboard.
    Table>profile———> save as view with name of Dataset
    want to do same for all 50+ tables

  • Josh Boxer
    Josh Boxer Administrator

    A View is a layer on top of a Dataset, so the method suggested above could be the first step and once the profile data exists create a View filtered to contain only the desired table results, clone that View update the filter etc.

    There is other functionality (Pushdown processing, Catalog and Governance) that might be useful/suitable, but without knowing what you are trying to achieve more broadly it is difficult to suggest. Once you have 50 table profile results are you putting those in a single Dashboard or are you planning on 50 Dashboards? Just curious how this would be useful to users?

  • Karthik_Anbusekar
    edited June 30

    Thanks Sidebotham,
    will try to apply your approach, using Power BI

  • You could also share that results dataset via Odata too, plenty of threads here go into detail.