I am wondering how to handle concurrency of data loading and reporting...

I know you've designed the round robin to switch loading data for every 15 minutes, what if the report last more than 15 minutes to generate, or let's say, just a second before the server1 get it's turn to refresh data, and there is a user report request come in and take 10 second to generate the report, then server 1 has to handle the concurrency of loading data and generating report...

that will lead to sqlserver locking mechnism and isolation level. what's your thought about it?

jiulu