How Many Ticks Does It Take DT To Load a DB Schema?

[EdCarden]

How Many Ticks (or seconds) Does It Take DT To Load a DB Schema?

I just timed it to find out myself and during normal business hours it takes Dependency Tracker more than 600 seconds (or greater than 10 minutes) to load a single DB Schema for a new Project.

While the previous version of DT may not have supported SQL Server 2008 R2 Reporting Services or SSIS integration it did at least run within a reasonable amount of time. I don’t recall exactly how long it took but I’m certain it wasn’t this long else I would have not purchased DT to begin with after the trial period.

Anyone else experience exceptional slow-downs in DT version 2.7 over a previous version? I have the same problem with SQL Prompt which is now to the point that its almost unusable.


NOTE: I actually took a 1 to 2 minutes longer to load the DB schema but I did not start timing the process until it had been running for a few minutes as I did not realize it was going to be this slow.

[james.billings]

Thanks for your post.
There's no easy answer to your question unfortunately - it sort of takes as long as it takes. The time will vary depending on the database and the server load, network connections, and several other factors. I'm not aware of it being obviously slower than earlier versions though.
How many objects do you have in your database?

You mentioned reporting services and SSIS - I didn't think dependency tracker supported these yet so they shouldn't make any difference?

As for Prompt being slow, it depends a little on how - is it slow starting up SSMS, or is it slow actually typing (characters appearing slowly etc)? If the latter, then upgrading your graphics card drivers can often help.