Louis Tochon works with a new bit of information:
The
Tableline looks like a normal scan of 330 pages. TheObjectline says the read walked through 220,000 row versions, 22 per row, because another session had updated these rows 22 times in a transaction it had not committed yet. The same read took about 117 ms of CPU, against 3 ms when nothing was pending.The
Objectline is new. It comes from the version store read metrics Dimitri Furman announced on the Azure SQL blog last week, which also appear in the actual plan XML returned by the server (SSMS 22.12.0 drops them, both in the graphical plan and in Show Execution Plan XML; copy the XML cell fromSET STATISTICS XML ONto see them), in four extended events, insys.dm_exec_query_statsand its procedure, trigger and function counterparts, and insys.dm_exec_requestsandsys.dm_exec_sessions(Microsoft documentation). For now they exist in Azure SQL Database and SQL database in Microsoft Fabric; Managed Instance and the next SQL Server version are announced to follow.When I recommend RCSI, the usual worry is the open transaction someone forgot in SSMS. These metrics let me check what it actually costs the readers.
The article looks to be AI-generated, but it does show off a new bit of functionality that I’d be happy to see spread beyond Azure SQL Database.
Leave a Comment