we are using the shared database development model with SVN. Ever since the last SQL Source Control Update (to Version 220.127.116.1129), we receive regularly error messages about failing to poll for 3 seconds. We have sent error messages about this to Redgate several times via the error reporting feature, though without a reaction so far. Also, when trying to commit, the commit dialog sometimes shows a message saying "Waiting for other operations to complete" indefinitely, keeping users from committing their changes.
Accidentally, I discovered the Asteriods easter egg while waiting for the commit dialog, but actually I'd prefer if I could commit my changes...
If nothing else helps, could you consider rolling back to handling the shared model like you did before version 3, or at least give the user a choice in this respect? We never had a problem finding out who changed what when committing changes, but now we regularly have problems committing changes, to an extent that renders SQL Source Control almost unusable.