如何使用T-SQL获取SQL Server活动监视器的输出?使用t-SQL获取SQL Server活动监视器的输出
回答
为了获得与活动监视器完全相同的输出;我创建了一个以下脚本。
如果使用此脚本,则不需要运行sp_who2或活动监视器。
我创建将显示以下事物的脚本:
- [会话ID]
- [用户处理]
- [注册]
- [阻塞者]
- [Head Blocker]
- [DatabaseName]
- [任务状态]
- [命令]
- [statement_text] - 它将显示当前正在执行的语句。
- [command_text] -----它将显示存储过程的名称。
- [总CPU(毫秒)]
- '经过时间(以秒为单位)'
- [等待时间(毫秒)]
- [等待类型]
- [等待资源]
- [存储器使用(KB)
- [主机名]
- [网络地址]
- [工作量组]
- [应用]
我的动态监控的脚本如下:
/* ACTIVITY MONITOR'S OUTPUT along with statement_text and command_text */ /* Processes */
SELECT [Session ID] = s.session_id,
[User Process] = CONVERT(CHAR(1), s.is_user_process),
[Login] = s.login_name,
[Blocked By] = ISNULL(CONVERT (varchar, w.blocking_session_id), ''),
[Head Blocker] =
CASE
-- session has an active request, is blocked, but is blocking others or session is idle but has an open tran and is blocking others
WHEN r2.session_id IS NOT NULL AND (r.blocking_session_id = 0 OR r.session_id IS NULL) THEN '1'
-- session is either not blocking someone, or is blocking someone but is blocked by another party
ELSE ''
END,
[DatabaseName] = ISNULL(db_name(r.database_id), N''),
[Task State] = ISNULL(t.task_state, N''),
[Command] = ISNULL(r.command, N''),
[statement_text] = Substring(st.TEXT, (r.statement_start_offset/2) + 1,
((CASE r.statement_end_offset WHEN - 1 THEN Datalength(st.TEXT)
ELSE r.statement_end_offset
END - r.statement_start_offset)/2) + 1), ----It will display the statement which is being executed presently.
[command_text] =Coalesce(Quotename(Db_name(st.dbid)) + N'.' + Quotename(Object_schema_name(st.objectid, st.dbid)) + N'.' + Quotename(Object_name(st.objectid, st.dbid)), ''), -- It will display the Stored Procedure's Name.
[Total CPU (ms)] = s.cpu_time,
r.total_elapsed_time/(1000.0) 'Elapsed Time (in Sec)',
[Wait Time (ms)] = ISNULL(w.wait_duration_ms, 0),
[Wait Type] = ISNULL(w.wait_type, N''),
[Wait Resource] = ISNULL(w.resource_description, N''),
[Total Physical I/O (MB)] = (s.reads + s.writes) * 8/1024,
[Memory Use (KB)] = s.memory_usage * 8192/1024,
--[Open Transactions Count] = ISNULL(r.open_transaction_count,0),
--[Login Time] = s.login_time,
--[Last Request Start Time] = s.last_request_start_time,
[Host Name] = ISNULL(s.host_name, N''),
[Net Address] = ISNULL(c.client_net_address, N''),
-- [Execution Context ID] = ISNULL(t.exec_context_id, 0),
-- [Request ID] = ISNULL(r.request_id, 0),
[Workload Group] = N'',
[Application] = ISNULL(s.program_name, N'')
FROM sys.dm_exec_sessions s
LEFT OUTER JOIN sys.dm_exec_connections c ON (s.session_id = c.session_id)
LEFT OUTER JOIN sys.dm_exec_requests r ON (s.session_id = r.session_id)
LEFT OUTER JOIN sys.dm_os_tasks t ON (r.session_id = t.session_id
AND r.request_id = t.request_id)
LEFT OUTER JOIN
(-- In some cases (e.g. parallel queries, also waiting for a worker), one thread can be flagged as
-- waiting for several different threads. This will cause that thread to show up in multiple rows
-- in our grid, which we don't want. Use ROW_NUMBER to select the longest wait for each thread,
-- and use it as representative of the other wait relationships this thread is involved in.
SELECT *,
ROW_NUMBER() OVER (PARTITION BY waiting_task_address
ORDER BY wait_duration_ms DESC) AS row_num
FROM sys.dm_os_waiting_tasks) w ON (t.session_id = w.session_id)
AND w.row_num = 1
LEFT OUTER JOIN sys.dm_exec_requests r2 ON (r.session_id = r2.blocking_session_id) OUTER APPLY sys.dm_exec_sql_text(r.sql_handle) AS st
WHERE s.session_Id > 50 -- Ignore system spids.
ORDER BY s.session_id --,[Total CPU (ms)] desc ;
我已经注释了一些列查询,如: - [打开交易次数= ISNULL(r.open_transaction_count,0), - [登录时间] = s.login_time, - [最后一次的请求开始时间] = S。 last_request_start_time, 所以,如果你想要也可以根据你的要求添加或删除列,你也可以过滤掉DatabaseName明智的数据。 我希望你们都会喜欢这个剧本。 –
不完全确定你在找什么,但是这应该给你类似于你在活动监视器上看到的东西(不完全但相似)。
SELECT
P.spid,
RIGHT(CONVERT(VARCHAR, DATEADD(MS, DATEDIFF(MS, P.last_batch, GETDATE()), '1900-01-01'), 121), 12) AS [BATCH_DURATION],
P.program_name,
P.hostname AS HOST_NAME,
P.loginame AS LOGIN_NAME
FROM master.dbo.sysprocesses AS P
WHERE
P.spid > 50 AND
P.status NOT IN ('background', 'sleeping') AND
P.cmd NOT IN
(
'AWAITING COMMAND',
'MIRROR HANDLER',
'LAZY WRITER',
'CHECKPOINT SLEEP',
'RA MANAGER'
)
ORDER BY 2
我们正在寻找SPID > 50
的原因是因为有ID小于50的过程属于内部操作。任何大于50的应该是用户操作。另外,你可以在数据库中看到所有的阻塞等,你可以尝试这样的事情。
SELECT
db.name AS DB_NAME,
tl.request_session_id AS REQUESTING_SESSION,
wt.blocking_session_id AS BLOCKING_SESSION,
OBJECT_NAME(p.OBJECT_ID) AS BLOCKED_OBJECT,
tl.resource_type AS RESOURCE_TYPE,
h1.TEXT AS REQUEST_QUERY,
h2.TEXT AS BLOCKING_QUERY,
tl.request_mode
FROM sys.dm_tran_locks AS tl
INNER JOIN sys.databases db ON db.database_id = tl.resource_database_id
INNER JOIN sys.dm_os_waiting_tasks AS wt ON tl.lock_owner_address = wt.resource_address
INNER JOIN sys.partitions AS p ON p.hobt_id = tl.resource_associated_entity_id
INNER JOIN sys.dm_exec_connections ec1 ON ec1.session_id = tl.request_session_id
INNER JOIN sys.dm_exec_connections ec2 ON ec2.session_id = wt.blocking_session_id
CROSS APPLY sys.dm_exec_sql_text(ec1.most_recent_sql_handle) AS h1
CROSS APPLY sys.dm_exec_sql_text(ec2.most_recent_sql_handle) AS h2
你可以结合这些来得到你正在寻找什么。 希望这有助于。
谢谢迈克尔.... –
但我刚刚创建了一个脚本,将提供与活动监视器相同的输出。 –
- 1. SQL Server 2008 Management Studio活动监视器
- 2. 活动监视器api获取摘要
- 3. 监视SQL Server 2005帐户活动
- 4. 用户访问SQL Server代理 - 作业活动监视器
- 5. 活动监视器
- 6. SQL Server 2005中的活动监视器问题
- 7. Sql Server活动监视器中的这个过程是什么?
- 8. 从SQL Server的活动监视器记录数据
- 9. 应用活动监视器
- 10. SQL Server Management Studio 2016→活动监视器→显示执行计划
- 11. Azure SQL数据库“活动监视器”
- 12. SQL Server状态监视器
- 13. ASP.NET Live活动监视器
- 14. SQL Server:使用TSQL变量时出错
- 15. 活动监视器查询
- 16. SQL查询以获取“活动监视器”中的作业步骤状态
- 17. 如何监视SQL Server中的活动连接池?
- 18. 捕获用于监视的ASP输出
- 19. 使用jquery监视用户的活动
- 20. 如何监视Oracle上的SQL活动?
- 21. 我试图说服我的IT部门的SQL Server活动监视器端口
- 22. QTKitServer保留在活动监视器中
- 23. 使用PDO和ODBC获取SQL Server输出参数的值
- 24. 如何使用tsql获取sql server服务信息
- 25. 监测或日志数据库活动使用SQL Server 2008
- 26. 活动监视器中的图标?
- 27. 使用WSO2业务活动监视器监视Oracle数据库的新记录
- 28. 如何决定在SQL Server活动监视器中杀死哪个进程?
- 29. 获取监视器计数
- 30. BizTalk商业活动监视器
哪一部分感兴趣?你想达到什么目的?会像讨论的免费存储过程一样(并且因为有了显着的改进)[这里](https://www.brentozar.com/archive/2014/10/why-i-dont-use-sql-server-activity-monitor /)有什么用处? – iamdave
“我只需要一个可以显示活动监视器输出的查询。”与所有正在运行的已处理信息一样,使用存储过程名称的活动查询,活动的昂贵查询,等待类型,已用时间,使用执行查询的人员,主机名称,应用程序名称以及执行查询的应用程序名称,以及我应该能够过滤数据输出。 –
运行在应用程序名称“Microsoft SQL Server Management Studio”上筛选的跟踪(Profiler或扩展事件)。这将捕获T-SQL活动监视器用于获取该信息, –