Returns a list of all SQL Server Operating System threads that are running under the SQL Server process.
Memory address (Primary Key) of the thread.
Indicates the thread initiator.
1 = SQL Server started the thread.
0 = Another component started the thread, such as an extended stored procedure from within SQL Server.
ID of the thread that is assigned by the operating system.
Internal status flag.
Address of the instruction that is currently being executed.
Time when this thread was created.
Amount of kernel time that is used by this thread.
Amount of user time that is used by this thread.
Memory address of the highest stack address for this thread.
Memory address of the lowest stack address of this thread.
Number of bytes that are committed in the stack.
Number of bytes that are actively being used on the thread.
CPU mask on which this thread is supposed to be running. This depends on the value in sp_configureaffinity mask configuration option.
Cached locale LCID for the thread.
Priority value of this thread.
Cached impersonation token handle for the thread.
Indicates whether this thread is using Win32 impersonation.
1 = The thread is using security credentials that are different from the default of the process. This indicates that the thread is impersonating an entity other than the one that created the process.
Operating system status of whether the thread is waiting on the loader lock.
Current Win32 fiber that is running on the thread. This is only applicable when SQL Server is configured for lightweight pooling.
Internal use only.
Internal use only.
Memory address of the scheduler that is associated with this thread. For more information, see sys.dm_os_schedulers (Transact-SQL).
Memory address of the worker that is bound to this thread. For more information, see sys.dm_os_workers (Transact-SQL).
Internal fiber context address. This is only applicable when SQL Server is configured for lightweight pooling.
Internal consistency pointer.
Upon startup, SQL Server starts threads and then associates workers with those threads. However, external components, such as an extended stored procedure, can start threads under the SQL Server process. SQL Server has no control of these threads. sys.dm_os_threads can provide information about rogue threads that consume resources in the SQL Server process.
The following query is used to find workers, along with time used for execution, that are running threads not started by SQL Server.
For conciseness, the following query uses an asterisk (*) in the SELECT statement. You should avoid using the asterisk (*), especially against catalog views, dynamic management views, and system table-valued functions. Future upgrades and releases of MicrosoftSQL Server may add columns and change the order of columns to these views and functions. These changes might break applications that expect a particular order and number of columns.
SELECT * FROM sys.dm_os_threads WHERE started_by_sqlservr = 0;