I have managed to avoid this behaviour from happening by re-installing the SQL tables from scratch.

I have not changed any of the .Net application settings (web garden was already set to 1).