There's reuseability client side too!!!

Have you tried doing the update in small batches (10 000 rows, wait 1 sec, next batch).

Then there's another... what are you trying to do... and what code are you using ATM?

If you run ONLY the proc without the set... on/off, does it work?

You're really better off using identity for this... I think it would be time to do the transfer. If you chose this method you can end up having 100s...

Is there a trigger on that table?

HTH..

From the same guy :

Dynamic Search Conditions in T-SQL

Arrays and Lists in SQL Server

The Curse and Blessings of Dynamic SQL - Injection

Looks like the parameters are in the wrong order... or the wrong datatype.

Sorry for the insistance... I have no other idea than that.

How do you usually call the proc?? Make sure you have all the code needed to make it run.

select stud_id, lname, fname, count(stud_id)

from stutable1

group by stud_id, lname, fname

having count (stud_id) >1

HTH... Books online is your best friend now .

Can you try using a domain account??

1 - It's possible but that shouldn't cause any noticable performance degradation (unless you have 1000s of open connections).

2 - Maybe, but we'd have to see the execution plan to...