Heh... Exactly... couldn't have said it better myself!

... and... GO WINGS! WOO-HOO!

Karthik...

What about you... you all set?

I delete dups like this all the time:

delete d

from table k

join table d on k.matching = d.matching

where d.primarykey < k.primarykey

And I could swear this is set based, but maybe it's...

Heh...you've got that right...

Thanks for the info, Ramesh... add one more chunk... the scripting options you told me about...

First, you must make the dates correct... the following code exemplifies the error... run it an see...

DECLARE @AnyDate DATETIME

SET @AnyDate = '12/8/2007'

SELECT @AnyDate + '11:59:59.999...

You bet, Sandy... thanks for the feedback.

If all the SKU's start with a numeric digit and nopne of the paths leading to the file have a digit anywhere in them, then the following demo code gives...

You are double posting... that'll get you thrown out of the "sandbox"... 😉

http://www.sqlservercentral.com/Forums/Topic431176-8-1.aspx

Of course the "code" must change... but the changes I made also make it more flexible...

DECLARE @Str VARCHAR(100)

SET @Str = 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'

SELECT LEFT(@Str,Number)

FROM...

Ummm... thanks Sandy, but that whole article is about how bad triangular...

I'll show how, you explain why...

DECLARE @Str CHAR(6)

SET @Str = 'ABCDEF'

SELECT LEFT(@Str,Number)

FROM Master.dbo.spt_Values

WHERE Type = 'P'

AND Number BETWEEN 1 AND...

Proof! Oh heck yeah... I'm working on a bunch of proof right now! 😉

GilaMonster (12/9/2007)

---

I still need to convert some of my crappy string manipulation functions to CLR. I'm betting on a CPU usage reduction if nothing else.

There are things that can be...

Thanks... I'll give 'er a whirl. Funny how they've so radically changed the terminology...

Think about it... 😉 See page 3 where they have the following code...

INSERT INTO [dbo].[Address_Temp] ( [FirstName], [LastName], [Address], [City], [State], [ZIP] )

SELECT [FirstName], [LastName], [Address], [City], [State], [ZIP]

FROM...