One of the most important tools for query tuning is ability to view execution plans. They are even portable; you can send an execution plan to get advice from someone who doesn't have access to the underlying data. Have you even considered that sensitive information might travel along with the plans? Hugo Kornelis explains how execution plans affect data protection.
2018-04-30
3,411 reads
By looking at a query execution plan, you can determine which steps are used to resolve the query. But what if you just want to find out what the query plans are for only the queries that are currently running?
2018-04-20
4,126 reads
Erik Darling shows how execution plan estimates suffer.
2018-04-18
3,318 reads
2016-12-14
1,165 reads
Execution plans explain all you need to know about query performance, and how to fine-tune. Sure, you can see them in SSMS, but what if you need to drill into to the important details? What about using DMVs, Extended Events or SET statements to get at the execution plans? To get the best use of execution plans you need to be able to get right information from the right plan at the right time. Robert Sheldon explains how.
2016-12-14
3,977 reads
When something's wrong with your database you need to be able to identify the primary pain points within SQL Server and get to the root cause of the problem fast. Grant Fritchey explains how you can use execution plans inside SQL Monitor to help quickly and simply identify the problem.
2016-12-09
3,837 reads
2015-12-14
1,468 reads
2015-12-07
1,372 reads
2015-11-30
1,311 reads
2015-11-19
1,615 reads
By Steve Jones
I had a conversation with a customer asking this question: how can I tell...
By Chris Yates
There was a time when the Chief Data Officer lived in the shadows of...
By Rayis Imayev
"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help...
Comments posted to this topic are about the item Create an HTML Report on...
Hi everyone I am getting an error when I create the index but I...
Good morning all, I have been running into a very random weird issue that...
I have two calls to the GENERATE_SERIES TVF in this code:
SELECT TOP 10 gs.value FROM GENERATE_SERIES(1, 10) AS gs ORDER BY NEWID () OPTION (RECOMPILE); go DECLARE @a int = 10; SELECT TOP (@a) gs.value FROM GENERATE_SERIES(1, @a) AS gs ORDER BY NEWID () OPTION (RECOMPILE);In the actual query plans, what is the estimated number of rows for each batch in SQL Server 2022? See possible answers