Viewing 15 posts - 54,511 through 54,525 (of 59,072 total)
Lowell (10/19/2007)
so...Your saying CLR's are for people who know sql, or people who don't know sql...I'm confused. 😉
By the way... this note cracked me up this morning... I almost...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2007 at 12:11 am
Heh... what'cha gonna do with a CLR that can't be easily done with good performance in T-SQL anyway? 😀 Think of it as an "omen"...;)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2007 at 12:09 am
Here is a Jeff Moden example I keep in my toolbox
Heh... thank you kindly for the "plug" 😀 Got a present for ya, MrPoleCat...
CREATE PROCEDURE dbo.AutoCrossTab
/**************************************************************************
Purpose:
-------
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2007 at 12:01 am
Went to the doctor and said "Doctor, when I hold my arm up like this (deomonstrating strange angle to arm), it hurts like hell". Doctor said, "Don't do that......
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 8:05 pm
Not sure why you're trying to do such a simple thing in such a difficult manner... but, using YOUR code...
SELECT * FROM #TestTable
WHERE Title LIKE '%'+@dummy+'%'[/b] or Title is null
OR...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 7:49 pm
I think you'll find the problem in one of the text columns... you may have some trailing spaces in some of the descriptions. You can check for those by...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 7:35 pm
I have checked all possible solutions for these but still get complaints from users about the slowness.
I'm thinking you haven't checked ALL possible solutions if you still have a problem...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 7:26 pm
Heh... can't believe you saved that list, Rudy 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 7:05 pm
Why not just include all non-working days including weekends and perform one check instead of two?
Larger number of rows? Correlated aggragate sub-query on large number of rows? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 6:46 pm
Greg Snidow (10/19/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 6:20 pm
David.Poole (10/19/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 5:49 pm
Jack Corbett (10/19/2007)
I really enjoyed the thread. A lot of good information and no one got personal as I have seen happen when...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 5:16 pm
Matt Miller (10/19/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 9:06 am
And, here's my "weekdays between dates" original post... just for reference 😀
http://www.sqlservercentral.com/articles/Advanced+Querying/calculatingworkdays/1660/
Part of what's so good about it is that it doesn't need to use a function... makes it very...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 2:12 am
Ok everyone... pay very close attention... I'm going to say it again until you get it...
[font="Arial Black"]CLR's are for people who don't know T-SQL[/font]
First, Matt... thank you, Sir, for providing...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2007 at 1:24 am
Viewing 15 posts - 54,511 through 54,525 (of 59,072 total)