Here is the quirky error that has caused a resources crunch on a SQL instance, Error : Process ID -2 is not a valid process ID . The actual issue occurred during an update to a table that has been used by Online application to update the action log, intially...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
by
on
Mon, Jul 27 2009
Filed under:
Filed under: sql server, dmv, error, best practices, spid, connections, code, msdtc, kill, rollback, orphan, distributed transactions