Skip to main content

Hi,

I have created a simple monitoring project with 12 catalog items for which I do only one dq check per catalog item + anomaly detection for this one attribute. However it seems that for this the system runs a full profile of every catalog item. Therefor this project is very heavy for the system to process. Can we adjust some settings so that the profiling is only run for this one attribute per table? Seems like a waste of resources this way.

kind regards, Jur Dördregter

Be the first to reply!