This isn’t necessarily a bad thing, but I’ve never heard of documentation that explains what’s rolled up into which groups. It took a whole lot of waits and rolled them up into ‘Buffer Latch’. I ran: exec sp_WhoIsActive Here I get specifics on exactly what type of wait is is and the related query.Īctivity monitor groups wait types. Here’s what Adam Machanic‘s free procedure, sp_WhoIsActive, shows for an instant in time during the workload. I ran: exec sp_BlitzFirst Hmmmm, that top wait type doesn’t seem like it was in the first screenshot at all. Here’s what our free procedure, sp_BlitzFirst shows for a 10 second sample while the workload is running. Here’s what Activity Monitor shows in SQL Server 2014: “Buffer Latch” must be my problem. My workload runs a query that’s very intensive against tempdb, and it’s really beating the SQL Server up by querying it continuously on seven threads. I fired up a workload with HammerDB against a test SQL Server 2014 instance. But I’m not a fan of Activity Monitor, a free tool in SQL Server Management studio, which helps you look at wait stats.Īctivity Monitor just doesn’t give you the whole truth. I also love analyzing SQL Server’s wait statistics.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |