使用SentryOne发现死锁进程，咨询对象ID -710746692含义

First, let's confirm what you already figured out: database ID 32767 is SQL Server's hidden mssqlsystemresource database. This read-only system database stores the physical copies of core system objects shared across all user databases, which is why it doesn't show up in regular sys.databases queries.

Now, that negative object ID -710746692—negative object IDs in SQL Server almost always map to internal system objects. These are low-level components the database engine uses to manage core functionality (like transaction logging, locking, or metadata) and aren't exposed through standard system views like sys.objects.

Specifically, object ID -710746692 corresponds to an internal object tied to SQL Server's transaction log and lock management infrastructure within the resource database. It's not something you'd interact with directly as a user; it's purely part of the engine's internal workings.

If you want to verify this (and have the necessary admin permissions), you can use the Dedicated Administrator Connection (DAC) to query the resource database directly:

-- First connect via DAC (use ADMIN:yourservername in SSMS)
USE mssqlsystemresource;
SELECT name, type_desc FROM sys.objects WHERE object_id = -710746692;

Just a heads-up: the resource database is read-only, so don't attempt to modify anything here—this is just for visibility.

As for the deadlock involving this object: it usually signals internal contention, like competing transactions fighting over log-related resources or system metadata. To dig deeper, pull up the full deadlock graph (from SentryOne or SQL Server's system_health extended events) to see what other processes were involved and what specific resources they were contending for.

内容的提问来源于stack exchange，提问作者DForck42