DQS Cleansing Task performance issue

Question

The DQS cleansing SSIS task used to run for 5 minutes. But suddenly it is running for more than 30 minutes. There is no change in the data as well as structure. The DQS cleansing tasks in all ETL jobs has the same issue. We suspect it might be cache issue but not sure how to proceed further. Please let us know if you have any solution

Answer 1

Hi @Surendra ,

There is a little message for us to analyze the issue.

You may enable the SSIS logging to find where is the bottleneck of the performance issue. Is it on source/ destination/ transformation ?

In the meantime, we could check the perform result of the ssis process contributes to the most CPU/memory on the server.

integration-services-ssis-logging

performance-counters

Regards，

Zoe

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hot issues October

Answer 2

Try cleaning the Project logs table. Every time the DQS component is invoked in a SSIS job, it will create log entries in the DQS_PROJECTS database. There is a script available in some sites that can be placed in a SQL job to periodically clean up the tables avoiding issues like this.
Also, include the DQS databases in your maintenance routine.