TheSQLGuru (1/26/2015)
That's quite interesting Dwain! I will have to set aside some time to break it down, and also modify it to work with the typical "UserID did something" scenarios I see at my web/mobile clients. I want to test scalability too.
Happy to be of help.
Note that I'm not sure it is 100% correct. It could depend on your definition of when you want to do the counting. For example, is a session active in a particular hour if it was active the entire hour or only part of the hour?
I think either can be handled though.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St