Database.Register taking a long time
Bruno.Latte
Posts: 8
Hello,
When I register our database (+- 400 tables), using the Register() method with default options, it takes a long time ( > 100000 ms or time to get some coffee).
Comparing a DB to a snapshot takes +- 10000 ms. That's not as long, but still quit some time.
Is there any way we can speed this up? Maybe use different options?
Grtz,
B
When I register our database (+- 400 tables), using the Register() method with default options, it takes a long time ( > 100000 ms or time to get some coffee).
Comparing a DB to a snapshot takes +- 10000 ms. That's not as long, but still quit some time.
Is there any way we can speed this up? Maybe use different options?
Grtz,
B
Comments
I was just wondering how long does it take when you use SQL Compare UI?
Does the time it takes to complete the action increases or decreases?
Please let us know how it goes.
Product Support
Redgate Software Ltd.
E-mail: support@red-gate.com
That's why I think there is something I'm supposed to use as an option or so in the Register() method.
Here's the basic code I use:
and the references I added to the project:
RedGate.Shared.ComparisonInterfaces RedGate.Shared.SQL RedGate.SQLCompare.Engine RedGate.Shared.Utils
When doing the actual comparison, the SQL Compare UI is able to compare the databases in about 2-3 minutes. The SDK takes about 15 minutes for the comparison.
For both the UI and the SDK tests, I'm using the same 2 databases running locally on a development SQL Server. I have exclusive access to the machine and to the SQL Server.
Any idea why registration and comparison of databases takes so much longer in the SDK than in the UI?
My code looks like this:
(I believe one of the reasons for this is that the debugger slows down exception handling a lot, since it has to stop the world and check if it needs to break on each exception)