I encountered an issue today which was only present when random sequences were not used. This is normally the case for sqlsrv, but I couldn't be bothered to debug with sql server (too slow to setup) so I just fudged the reset_all_database_sequences() function to not reset sequences in this instance.

It's quite useful to do when tracking down these problems, so I'd suggest that we make it a setting of some kind.