The short answer: in the real world, only the first column works. When SQL Server needs data about the second column, it builds its own stats on that column instead (assuming they don’t already exist), and uses those two statistics together – but they’re not really correlated.
2026-04-29
2024-11-15
416 reads
2024-11-01
350 reads
2024-10-11
344 reads
2024-10-04
426 reads
2024-05-17
337 reads
2024-01-03
386 reads
2023-12-18
367 reads
2023-12-04
395 reads
2023-11-20
346 reads
It’s time for T-SQL Tuesday again! And we’re almost to number 200! T-SQL Tuesday...
You kick off a distributed job expecting it to finish in minutes — but...
A while ago we suddenly had an error while trying to deploy one Fabric...
Tlp/Wa_Cs:0817-866-887. Jl. Jenderal Sudirman No.39, Krobokan, Kec. Semarang Barat, Kota Semarang, Jawa Tengah 50141...
Comments posted to this topic are about the item Secure Cached Plans
Comments posted to this topic are about the item Complex Data Processing with dbt...
The DMV, sys.dm_exec_cached_plans, contains rows for each cached plan on an instance. In Azure SQL Database, not every used has rights to every database, as there does exist an instance behind each database. How is security handled for this DMV in Azure?
See possible answers