*This post is locked for comments
My understanding is that Row Versioning is defaulted to off. We have this setting set to on on our Dynamics GP databases. The person that did the initial installation of GP is no longer here nor are we sure why this would have been turning on. We are having performance issues with GP. we only have 13 users. TEMPDB has filled up several times. We would like to turn this feature off, but again not sure why someone would have turned it on. Would there be an issues with us turning it off now.
Thanks
Row versioning is not necessarily a switch you just turn off or on. It’s related to the concurrency model you are using. In SQL there are two concurrency models: pessimistic and optimistic. In pessimistic when a user is modifying data, any other access whether another writer or reader are blocked until the data modification is done. With optimistic SQL makes a copy of the data before any changes and submits that copy to any readers (writers of course are still blocked). There are also other things to consider like Isolation levels. If your company makes lots of data changes you may want to stick with Optimistic. If you don’t make many data changes you may be able to use Pessimistic. You should do some research and decide how you want to handle Concurrency at your firm and understand how SQL handles row versioning with regard to the tempdb. You may also want enlarge your tempdb.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
