It surely is addictive... I wouldn't call it a drug thaugh.. doesn't have as many side effects!!!

He's never really off .

And what was the solution?

Since you just stated that you were a beginner, I'll say this part again. UNLESS for much improved performance, this is the type of operation that is better handled...

Not sure many would fall for that one...

How many coders do you expect ignore that the table can be aliased?

We could always sugget it to Steve.

You can create a function to return the formated date since it's probabely gonna be reused later.

Otherwise it's gonna depend on the rest of the application... You're pretty much...

Have you ever used sql server??

Btw dates often make very good indexes... maybe not quite as good in this case since there are only 12 values/year but I think it's still better than a char.

Hmm, I think that having it as a date is still the best option.

You can recreate the date using the month and year like so :

Declare @Year as int...

How is the expiration date kept on the server?

have you tried moving this code :

delete from rt_edt

where mid=@mid and (src is null or src='')

in here

IF len(@row) <= 16

...

I would look into the functions: datediff, datepart and dateadd in the books online. This is pretty all you'll be needing.

Any specific problem you need help with?

Can you recode the stored proc in pseudo-code like :

declare var.

open cur

delete from

while not

do 1....

I'm just not sure enough of what you're trying to do in this proc.

It's the alias name for the derived table.

(

select * from zzA

union

select * from zzB

)

becomes a virtual table in the select that can be used like any real table.

DERIVEDTBL just happens...

What you're saying makes sens. But as I said before there's no point in running a command like "Delete from a where col = @col" more than once if @col...