August 1, 2014 at 2:09 am
Hey all,
I am shortly embarking on a project to redesign an ETL process.
Currently issues can be cause by end users running reports (SSRS, EXCEL) while a table is updating.
There is currently a report that shows end users when there reports are ready, but still sometimes they try beforehand and it can cause blocking.
So how do i go about stopping this? I dont want to stop users getting into the database completely as they need to be able to run the report they require when its ready - even if other stuff is still running.
The only thing i can think of is doing a NOLOCK on the reporting. Is there any other options?
Dan
August 1, 2014 at 4:45 am
danielfountain (8/1/2014)
Hey all,I am shortly embarking on a project to redesign an ETL process.
Currently issues can be cause by end users running reports (SSRS, EXCEL) while a table is updating.
There is currently a report that shows end users when there reports are ready, but still sometimes they try beforehand and it can cause blocking.
So how do i go about stopping this? I dont want to stop users getting into the database completely as they need to be able to run the report they require when its ready - even if other stuff is still running.
The only thing i can think of is doing a NOLOCK on the reporting. Is there any other options?
Dan
Quick thought, have you looked into using the snapshot transaction isolation level or Optimistic Locking[/url]. In this situation you DO NOT want to use NOLOCK!
😎
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply