Thank you for reaching out on the Redgate forums and sorry to hear you're running into some performance issues with SQL Dependency Tracker!
To help us narrow down the cause in this case:
- Are you able to try SQL Dependency Tracker on the same database but from another machine?
- Is it just as slow on smaller databases?
- How much CPU and RAM is it using while it's generating the graphs?
If possible are you able to enable verbose logging and recreate the slow speed and provide the logs.
Logging was disabled after v3.3.4 due to an ongoing compliance update, if you have patched past this version can you please downgrade so logs can be created
I have created a file upload for your logs so they don't have to be shared over the public forum
This link will be active for 7 days
In a number of cases, SQL Dependency Tracker is not able to fully process large and/or complicated databases effectively and will experience the slowness that you are describing.
We recommend reducing the amount of objects in your project to see if this improves performance as well as tweaking the depth level of objects that are added through the Project Options > Diagram options menu
Tips and how-to guides for Redgate products
Ask, discuss, and solve questions about Redgate's tools
Meet us at an event, get sponsored, and join our Friends of Redgate
In-depth articles and opinion from Redgate's technical journal