Comments for Brad Corbin http://bradcorbin.net Brad Corbin on SQL Server Thu, 28 Jan 2010 13:55:05 -0700 http://wordpress.org/?v=2.9.2 hourly 1 Comment on Identifying the High CPU SQL Instance by Michael J Swart http://bradcorbin.net/2010/01/identifying-the-high-cpu-sql-instance/comment-page-1/#comment-13 Michael J Swart Thu, 28 Jan 2010 13:55:05 +0000 http://bradcorbin.net/?p=61#comment-13 That's awesome. As an alternative to task manager, I use process explorer. An old article of mine ( http://michaeljswart.com/?p=12 ) includes a 20 second video showing how I find the top cpu consumer and instance name. That’s awesome.
As an alternative to task manager, I use process explorer.
An old article of mine ( http://michaeljswart.com/?p=12 ) includes a 20 second video showing how I find the top cpu consumer and instance name.

]]> Comment on New SQL Server Blog! by Lee http://bradcorbin.net/2009/09/new-sql-server-blog/comment-page-1/#comment-8 Lee Fri, 16 Oct 2009 12:51:50 +0000 http://bradcorbin.net/?p=5#comment-8 Looking forward to some great blog postings! I am in the process also of sqlserverpedia syndication. Best regards, Lee Everest Looking forward to some great blog postings! I am in the process also of sqlserverpedia syndication.

Best regards,
Lee Everest

]]> Comment on The Phantom Query by Brad Corbin http://bradcorbin.net/2009/09/the-phantom-query/comment-page-1/#comment-4 Brad Corbin Wed, 30 Sep 2009 21:06:02 +0000 http://bradcorbin.net/?p=15#comment-4 Yep, pulling that term out should be equivalent, and (I would guess) gives you have a chance of using an index on FROM_DATE, if there is one. Yep, pulling that term out should be equivalent, and (I would guess) gives you have a chance of using an index on FROM_DATE, if there is one.

]]> Comment on The Phantom Query by Brad Schulz http://bradcorbin.net/2009/09/the-phantom-query/comment-page-1/#comment-3 Brad Schulz Wed, 30 Sep 2009 19:37:25 +0000 http://bradcorbin.net/?p=15#comment-3 Hi Brad... I think your final WHERE clause is equivalent to the following: WHERE GETDATE()>=FROM_DATE AND (TO_DATE IS NULL OR GETDATE()<=TO_DATE) or even the initial query could just be changed to the following to imply the maximum allowable SMALLDATETIME value if TO_DATE is NULL: WHERE GETDATE() BETWEEN FROM_DATE AND COALESCE(TO_DATE,'20790606') (I tend to prefer COALESCE to ISNULL) I tried to run time tests on all three approaches, but the results I got (on a million-row table) were inconclusive. They're all pretty much interchangeable I suppose. Thanks for an interesting first entry. I'm looking forward to reading more in the future... --Brad Schulz Hi Brad…

I think your final WHERE clause is equivalent to the following:

WHERE GETDATE()>=FROM_DATE
AND (TO_DATE IS NULL OR GETDATE()<=TO_DATE)

or even the initial query could just be changed to the following to imply the maximum allowable SMALLDATETIME value if TO_DATE is NULL:

WHERE GETDATE() BETWEEN FROM_DATE AND COALESCE(TO_DATE,'20790606')

(I tend to prefer COALESCE to ISNULL)

I tried to run time tests on all three approaches, but the results I got (on a million-row table) were inconclusive. They're all pretty much interchangeable I suppose.

Thanks for an interesting first entry. I'm looking forward to reading more in the future…

–Brad Schulz

]]> Comment on New SQL Server Blog! by Brent Ozar http://bradcorbin.net/2009/09/new-sql-server-blog/comment-page-1/#comment-2 Brent Ozar Wed, 30 Sep 2009 11:25:45 +0000 http://bradcorbin.net/?p=5#comment-2 Boy, do I know what you mean about life getting in the way. It's funny how that works. Glad to see you starting to blog! Boy, do I know what you mean about life getting in the way. It’s funny how that works. Glad to see you starting to blog!

]]>