In addition to the tests, think it through. Is it storing just the data in a clustered index or might there be something in addition?

You should set up a server-side trace that starts around 5AM and ends around 6AM so you can observe the queries running on the server. Here's the basics...

You just mean grouping within SSMS? As Beatrix said, it doesn't do that. No way for you to do it really either other than what she says.

Yeah, pretty good. Intro level sessions are always good.

Other stuff  = Business definitions in regards to amount of data loss, recovery time, etc., etc., because it's as much...

If you're on the eastern seaboard of the US and you hear a grinding noise, it's just my teeth.

OK. Not sure what that script has to do with things.

You're saying that  on a server with zero actual load, a query constitutes 56% of the perceived CPU...

Ah, I think I better understand. Well, that can be tough. If the applications all supply their application name with their connection activity (not required), then you can monitor connections...