HTH .

Still wanna know what it really means (have a clue but not too sure).

Sorry I mislead you a little bit because I didn't remember what had to be done :

ALTER procedure p_copyproduct

(@newProductId int, @prevProductId int)

as

SET NOCOUNT ON

Insert into dbo.ProductAttribute (ProductId ,...

What's that really? ("ClubBat")

I didn't have that approriate training as you call it. But i'm learning new stuff everyday so this set thing is getting pretty deep in my head

What do you want to do exactly?

You have to avoid doing the select in the first place.

You have to do :

If not exists (Select * from dbo.YourTable where id = @Id)

begin

call create statement

end

select statement here.

The compound index could have had the exact same effect. This would have been the case because all the values needed to generate the select would have been retrieved...

Product a cannot be blue, black and blue again. Each attribute must be unique to the product in that table.

That message was more directed towards the original posters of this thread.

Conclusion to this real world case.

Procedural Approach : 2+ hours

Set based approach (even with lots of dynamic sql) = 26 secs

So that would make this method 277+...

HT almost H. Hey at least I started the whole thing .

Thanx Noeld, I just wasn't getting what he wanted to do with...

This sounds plausible... but I wanted to be sure that this was the right answer .

Hey dude you're selecting from the same table you are inserting to, that can't insert rows and not cause duplicates.

Try the trace, catch the statements and reexecute them, maybe the error will be usefull there. I'm in no way an expert in dts so I can't offer much...