A. This is a bug in SQL Server. Chances are you are using a temporary table with an identity column. You can re-write the SP or try the latest SQL Service pack. Microsoft will eventually fix this one.