SQLServerCentral / Discuss Content Posted by Grant Fritchey / Article Discussions / Article Discussions by Author / SSC Clinic: Finding the rogue query / Latest Posts

RE: SSC Clinic: Finding the rogue query

Neha05 — Tue, 25 Dec 2012 08:41:49 GMT

Good article.

RE: SSC Clinic: Finding the rogue query

Grant Fritchey — Fri, 14 Sep 2012 06:02:58 GMT

[quote][b]OceanDeep (9/13/2012)[/b][hr]Where are those analysis pages coming from? Is it a feature in SQL activity monitor? If so, please advice the proper steps to do what you show. If you are using a tool to build sll that, let me know what u use.[/quote]It's all from Red Gate SQL Monitor. You can see it in action against SQL Server Central here at [url=http://monitor.red-gate.com]monitor.red-gate.com[/url]

RE: SSC Clinic: Finding the rogue query

Tom_Sacramento — Thu, 13 Sep 2012 10:46:48 GMT

Check the stats on the table.Look at execution plan for bootlenecks/scans etcVeryify order of Where parameters works to effectivelyCheck the indexes for existence and fragmentation.Definitely pre calc the date comparision.If stored procedure then after verifying stats are up to date then I'd do an sp_recompile on the sProcMuch to learn, teach me Yoda

RE: SSC Clinic: Finding the rogue query

Dean Cochrane — Thu, 13 Sep 2012 09:20:53 GMT

[quote][b]tolga.kurkcuoglu (9/13/2012)[/b][hr]from the name of the table, I guess there is a considerable amount of records in it.It looks like it, unneccessarily, computes the dateadd function for each row.you might store the value in a variabledeclare @yesterday smalldatetime = dateadd("d", -1, getdate())and use it like... and date > @yesterday[/quote]I doubt that that will make any difference. I'd be very surprised if the engine calls the dateadd function more than once. In the optimization phase it will do what you suggest. It just won't tell you about it.

RE: SSC Clinic: Finding the rogue query

OceanDeep — Thu, 13 Sep 2012 08:36:54 GMT

Where are those analysis pages coming from? Is it a feature in SQL activity monitor? If so, please advice the proper steps to do what you show. If you are using a tool to build sll that, let me know what u use.

RE: SSC Clinic: Finding the rogue query

donald.maslanka — Thu, 13 Sep 2012 06:45:29 GMT

"The measured average is only .4 at peaks around that time, so we're not looking at multiple processes fighting over the processor. That means one event is causing the problem."How did you know it was only one event? Or that it wasn't multiple processes?Thanks.

RE: SSC Clinic: Finding the rogue query

Grant Fritchey — Thu, 13 Sep 2012 06:03:00 GMT

Good suggestion. I haven't started tuning the query yet, but that's absolutely one of the changes I'll make. Thanks.

RE: SSC Clinic: Finding the rogue query

tolga.kurkcuoglu — Thu, 13 Sep 2012 02:28:19 GMT

from the name of the table, I guess there is a considerable amount of records in it.It looks like it, unneccessarily, computes the dateadd function for each row.you might store the value in a variabledeclare @yesterday smalldatetime = dateadd("d", -1, getdate())and use it like... and date > @yesterday

SSC Clinic: Finding the rogue query

Grant Fritchey — Thu, 13 Sep 2012 00:03:25 GMT

Comments posted to this topic are about the item [B]SSC Clinic: Finding the rogue query[/B]