We call it the "Easy button"...

Thanks Carlos!  Comments like yours make it all worth while!

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...

Nicely done...

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"......

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...

Dang... Your name is even posted right under your handle, too!  I missed that... sorry, Gail.

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...

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...

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...

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...

I'm still curious... why did you want to join two tables that have nothing in common to join on?

That's what I thought... thanks for the feedback, Trigger.

Just a reminder, folks... xp_CmdShell requires SA privs or a proxy login that has SA privs.

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"...