Viewing 15 posts - 58,486 through 58,500 (of 59,067 total)
Thanks Carlos! Comments like yours make it all worth while! ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2006 at 5:44 pm
There's a couple hundred different ways of doing this... here's one...
--For NANPA numbers only...
CREATE TABLE #example (ID INT IDENTITY(1,1), PhoneNum VARCHAR(15))
INSERT INTO #example (PhoneNum)
SELECT '2223334444' UNION...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2006 at 5:37 pm
Nicely done...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2006 at 7:22 am
Maybe, but the use of the "double parameter" isn't really going to slow anything down here... I am confused by your posting, though... you say "giving me the first Monday"......
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2006 at 8:16 am
Easy...
1. Any decimal dollar amount greater than x.xx5, regardless of the number of decimal places, will be rounded up to the penny.
2. Any decimal dollar amount less than x.xx5, regardless...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2006 at 12:15 am
Dang... Your name is even posted right under your handle, too! I missed that... sorry, Gail.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2006 at 6:10 am
GM beat me to it but using his test, I came up with the same correct results all 3 times...
SortOrder,Letter
0,e
0,b
1,a
1,f
1,c
2,d
2,g
Ryan, Yep, I tried it and you are correct (I forgot...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2006 at 7:12 am
As the article warns, this method makes use of a correlated subquery that forms a triangular join which is half a cross join. It will crush any hopes of performance...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2006 at 8:35 pm
You do not need to enable full text features to use SOUNDEX or DIFFERENCE...
DECLARE @Str1 VARCHAR(100)
DECLARE @Str2 VARCHAR(100)
SET @Str1 = '129 Green Ave'
SET @Str2 = 'Green...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2006 at 8:24 pm
If tl.Date is a DateTime column to begin with, you don't need to do any of that.... the Order By tl.Date will work correctly even though you've Cast it in...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2006 at 8:03 pm
I'm still curious... why did you want to join two tables that have nothing in common to join on?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2006 at 7:58 pm
That's what I thought... thanks for the feedback, Trigger.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2006 at 7:43 pm
Just a reminder, folks... xp_CmdShell requires SA privs or a proxy login that has SA privs.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2006 at 3:25 pm
Pat,
Basically, any legal expression may be used so long as it does not refer to another table. Cast and Case may be used. SELECT may not because it's a "clause"...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2005 at 1:02 pm
Nope... it's not... SET ls_action=0 will fail in the absence of other code. You either have to declare ls_action as variable (don't forget to add the @ sign) or you have...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2005 at 12:37 pm
Viewing 15 posts - 58,486 through 58,500 (of 59,067 total)