January 30, 2012 at 2:55 am
Hey all,
I have a report sever. Overnight rebuild from external source. During the day it has no updates.
For the reports - would i see an improvement if i set the isolation level (on the SP for each report) to Read uncommitted? Obviously there would be no "uncommitted" to read - and as far as i can tell no dangers of phantoms etc.
I have a second server. This however can get updates during the day - however i while the updates take place i dont want the reports to not work. Does snapshot isolation sound the best for these? As msdb says "A system that has multiple readers and a single writer (such as the replicated reporting system in the scenario section earlier in this paper) will not encounter conflicts."
http://msdn.microsoft.com/en-us/library/ms345124(v=sql.90).aspx
So if the report was run mid way through an upload (which are wrapped in a transaction) would i get a clean read as per the database BEFORE the upload?
Am i reading this correctly?
Any help much appreciated.
Dan
January 30, 2012 at 4:20 am
you can use query hint " with nolock" in your select queries.
----------
Ashish
January 30, 2012 at 4:45 am
Ashish,
Sorry for which of my two scenarios are you sugguesting using nolock?
Thanks for your help
Dan
January 30, 2012 at 5:24 am
Its about the point where you planning to change the isolation level to read uncommited.
----------
Ashish
January 30, 2012 at 9:14 am
Ok - for the read uncommited (my first issue) i was planning on the stored procs that read the data for the reports to set it in there.
Dan
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply