We're looking to implement MVCC/READ_COMMITED_SNAPSHOT in our high-transaction databases. We understand from documentation that this will require more tempdb space to manage the snapshots of the data for the various sessions, but it will address contention
issues that for our purposes can't be avoided without compromising result set integrity. I'm trying to figure out a good way of estimating the new tempdb requirements. I'd appreciate advice from others who have implemented this feature on how to approach the
question of sizing.
↧