Multiple Asynchronous Database.Register calls
What we've found is that when we asyncrhonously register 2 databases
using a delegate for the Database.register method and callbacks for the delegate completion, performance benefits are only obtained if the 2 database objects refer to databases on distinct servers. If the database objects are on the same server (different databases obviously!), no benefit of running the register process in parallel is obtained.
Can anyone explain why this should be. My only guess is that there is some form of lock going on in the depths of Database.register method which in effect blocks the 2nd parallel registration attempt until the first completes.
The reason for wanting to do this is that we actually require to sync 3 databases and with a time penalty of 40s per database registration, by running registration in parallel, we can save 80s of waiting around time for the user.
Any input would be greatfully appreciated.