September 3, 2006 at 7:30 am
The article certainly gives a slant on object usage, however I'd suggest a sql statement vs reads, writes, cpu, duration is of much greater value
How do you measure this part...aswell..that be useful to
October 17, 2006 at 2:02 pm
My approach was to use the Scans: Stopped event class to capture the scans. It includes the number of pages read in each scan. I use that number multiplied by the number of scans to calculate the data flow.
August 30, 2007 at 7:51 am
Awesome article - just have to see if I can truly put it to practical use.
September 4, 2007 at 5:05 am
Really pedagogical - easy to follow flow of article/method, and very nice with a proposed solution!
March 30, 2009 at 10:06 am
Can someone please tell me how the raw data from the (SQL Profiler) gets into the table IndexCapture?
Thank you,
Anil.
July 21, 2009 at 8:30 am
The two Screen Shots are not getting displayed under "Analyze the Results" section. Is anyone else facing the same problem?
July 23, 2009 at 7:45 pm
From the author, many years too late, but still worth commenting on: Yes, indeed sharp readers, the aggregate clause in "Summarize the Data" shoud be "count(*)" and not "sum(*)"! I still do not know how I let that slip through! Many thanks to you for catching that and passing along. To all, I've enjoyed your comments and I especially appreciate those who have taken this a step beyond (or many more steps). That is precisely what I had hoped to accomplish with this article: to give folks a starting point that they could utilize in their own work. Now that we have SQL Server 2005, the included system views take care of a lot of this, but it is still useful for anyone who is still running SQL Server 2000.
October 21, 2013 at 4:48 am
Mike Morin-219647 (7/23/2009)
From the author, many years too late, but still worth commenting on: Yes, indeed sharp readers, the aggregate clause in "Summarize the Data" shoud be "count(*)" and not "sum(*)"! I still do not know how I let that slip through! Many thanks to you for catching that and passing along. To all, I've enjoyed your comments and I especially appreciate those who have taken this a step beyond (or many more steps). That is precisely what I had hoped to accomplish with this article: to give folks a starting point that they could utilize in their own work. Now that we have SQL Server 2005, the included system views take care of a lot of this, but it is still useful for anyone who is still running SQL Server 2000.
+1 .... beside that very nice article
Viewing 8 posts - 16 through 22 (of 22 total)
You must be logged in to reply to this topic. Login to reply