Closed philcart closed 2 years ago
@philcart this is a SQL Server bug that has impacted several analysis procs and monitoring tools. You should open a ticket with Microsoft.
@erikdarlingdata, similar problem here after upgrading from SQL 2014 to SQL2019. Didn't have this problem in 2014.
Who Is Active? v12.00 (2021-11-10) Microsoft SQL Server 2019 (RTM-CU14) (KB5007182) - 15.0.4188.2 (X64) Exception Address = 00007FFE77EE3C1A Module(sqlmin+0000000000033C1A) 2022-02-27 19:42:31.13 spid604 Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION 2022-02-27 19:42:31.13 spid604 Access Violation occurred reading address 0000000000000030 2022-02-27 19:42:31.13 spid604 Input Buffer 92 bytes - 2022-02-27 19:42:31.13 spid604 EXEC [dbo].[sp_CaptureWhoIsActive]
CU15 solved this issue for me @erikdarlingdata .
Hi All
Hope someone is able to provide some insight and potential resolution for a problem we're experiencing
This problem has showed up on three servers now. Each occurrence has started with an exception being generated by the SPID running sp_WhoIsActive. There isn't any specific timeline (runtime, time of day, etc...) and the workloads on each of the servers is very different. On two occasions the SQL Server process was terminated, and another the service had to be manually restarted as it was in a CPU spin. Other occasions have left the server generally unresponsive until the offending SPID was killed off.
Running
sp_WhoIsActive is being run in a SQL Agent job to capture any blocking activity occurring on the server. The job runs every minute and has two steps, 1) Capture sp_WhoIsActive data, 2) Analyse and raise an alert if blocking is detected.
The command to capture the data is as follows,
This is the structure of the workBlockingCapture table,
The following the latest exception event that occurred,
If any further details are required, I'm happy to provide what I'm able to.
Cheers Phil