Thanks for the response, I'm not sure I fully follow, do you have any links to articles explaining more or something?

Thanks.

Okay, well below is a table I've just knocked up, using real dates in the query I have, it should illustrate the point - some responses are within an hour...

That's a very comprehensive calendar table! Thanks for the linkage. The calendar table isn't so much the issue, how I use it is the issue!... I could knock up a...

Thanks Lowell, I don't write anything except SQL so some of this is beyond my current skill set, however, the article is very interesting, some of our vb.net developers could...

Wasn't necessarily 'playing' in the live environment! The query and hence proc were created in a dev environment and tested, sadly it's not that representative of the live environment. Taking...

Not sure posting the code would make a massive difference, the code alone (within the proc) is fine and runs quick enough, it's just the act of running it as...

21 seconds down to 4 seconds on the live environment? I'll take a bit of that!! Thanks for the suggestion, it's made a huge difference.

@Recurs1on: this seemed to work for me on the few examples I tried, however, I considered whether ALL of the html would be correct, as it's users (not...

That sounds like quite a scary outcome, compared to the possibility of dirty reads!

I was looking manually in some of the report server tables just yesterday and I noticed what a wealth of useful information was contained within them. I was going to...

Yes, a lot! That's really great, thank you for that brief summary. Perhaps you could see where I was going with my fears? - I had visions of...

So if you just turn RCSI on, what are the implications for running a query against say a table who's data changes virtually constantly (think a bit like weblogs or...

Taken a different approach to this... I setup a test SP and within the SP I calculated a date diff based on days and reset the date parameters based on...

Just wondering what you'd make of using nolock in this situation...

You want to obtain the most recent communication and a count of communications for a particular customer.

Running that query...

Are there any implications for database storage and or disk use of going down the snapshot route? That's what seems to be ringing some bells?