|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Profiler Error ColumnI'm capturing Profiler traces for resource intensive SPs and T-SQL statements/batches. I know a DELETE failed earlier today - the 2 million records it was supposed to delete were still in the table it was deleting from. The error column of the Profiler trace for this DELETE statement =2. When I looked at BOL Profiler>Data Columns, Error has the following entry: ------------------- Data column - Column number - Description "Error - 31 - The error number of a given event. Often this is the error number stored in sysmessages." ------------------- When I ran the following on the Production DB server and the server on which the trace was being captured, 0 rows qualified. select * from master..sysmessages where error = 2 What do error numbers 2 and 0 signify? (I've tried to search for this information but couldn't find anything pertaining to my issue). Thank you, Smitha |
|||||||||||||||||||||||