How to schedule profiling of specific schema in the database Or subset of that schema if schema is too big.

Hi ​@Ojaswini -- while you can’t schedule profiling of a selected schema from the web app, you could use the following GraphQL query to trigger profiling of selected catalog items programmatically. 

query profiling (
  $gid: GID!
  $configId: GID!
) {catalogItem(gid: $gid) {
    gid
    profile(defaultCredential: true, configId: $configId)
     {gid}
     }
    }

Using a ONE Desktop plan, you can export the list of locations (schemas) and the list of catalog items, then filter down to the list of schemas you’re interested in, and then pass the resulting list of catalog items to the JSON call step with the above query. You can further automate this with a scheduled orchestration workflow. Have you created similar plans and workflows before? Let me know if you have questions, I’ll be happy to point you to some more info!

Hi,

We have the same requirement: we would like to schedule profiling only for Catalog Items belonging to a specific schema, while completely excluding Catalog Items from other schemas in the same source.

We understand the GraphQL workaround described above. However, we have also discussed this with Ataccama Support (SR-36020), and they mentioned that it might be possible to use Documentation Flow configuration and a metadata field common to all Catalog Items from the selected schema.

As we understand it, this would allow matching Catalog Items to be fully profiled, but Catalog Items from other schemas would still be processed using sample profiling.

Is there a configuration option in the Documentation Flow to completely exclude Catalog Items from other schemas from the scheduled profiling run, rather than profiling them in sample mode?