Database Register Performance

Neil Davidson

You're right - it is extremely painful. It seems to be a combination of how one of the third party components we use behaves and a bug in the IDE. The way we get round it at Red Gate is to start the program we're debugging via a CTRL-F5 (so it isn't being debugged) and then putting a System.Diagnostics.Debugger.Break() after the Database.Register where we want to break. Alternatively, you can attach the debugger manually after the database has been registered.

This is something that we intend to fix.

burtonrodman

I may have a possible explanation for the slowness.

The application that i am working on automates SQLCompare, SQLDataCompare, SQLPackager and Visual Studio to build numerous packages with a customized template.

I had set Visual Studio to break on all CLR exceptions and it kept breaking on the Database.Register with an unknown exception type with a message of Mismatched token. This through me for a loop at first because i had forgotten that i had set it to break on all exceptions, but once i figured out what was going on, it reminded me of this post.

HTH
burt