60
Hello, we are running Dynamics GP 2013 on SQL 2012 and are seeing some intermittent blocking at the database level. I believe that some of this can be eliminated by turning on Read Committed Snapshot Isolation on the database but I'm wondering if there are any best practices available on this topic.
TIA,
Kevin Eckart
*This post is locked for comments
Hi Kevin,
I'm looking at RCSI for our GP 2013 install... Wondering if you ever went there, and if so - how did it go?
Thanks,
Bill
For something this fundamental I'd seek an authoritative answer from Microsoft. It seems very tempting, but could have unanticipated consequences at the application level if the application is not written and tested against it.
-Also GP at the application level GP is specifying read committed in its transactions, I don't know enough about how that plays out with the database isolation level at snapshot read committed...
So I'm answering to warn others reading this not to jump on this bandwagon without due care, however if you pursue this and find it actually is OK, I would love to jump on your band wagon too!
Tim
Hi Jonathan, thanks for your response. Many of the blocks we are seeing come from running very long reports via SmartList in GP and some third party reporting apps. It's a very intermittent issue and I'm not hearing a lot of complaining from the users but I thought I might be able to handle it via RCSI. From a purely DBA perspective, I know that RCSI will increase the usage of TempDB, but it's backed by SSD's, so speed shouldn't be an issue there.
I am not aware of anything from Microsoft that answers your question but I believe GP has methods internally for dealing with concurrency. Can you reproduce the blocks that occur and run a SQL trace to see where / when the block occur? Have you recently introduced any new 3rd party apps to the environment?
#1
André Arnaud de Cal...
291,711
Super User 2024 Season 2
#2
Martin Dráb
230,458
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
