Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit 223fc79

Browse files
SQL2017 query_post_execution_plan_profile overhead
following QFE 13515392. Based on Jayc input : "On SQL17 however, lightweight profiling is OFF by default and query_post_execution_plan_profile depends on lightweight profile. When you turn on/off this XEvent, the server will turn on/off lightweight profiling. Every time you change lightweight profiling, the server needs to invalidate the execution plan cache. So it is really bad idea to change this status frequently. This is what the customer is doing every couple of minutes. It would be better to turn lightweight profiling ON with TF7412."
1 parent fcf78c3 commit 223fc79

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

docs/relational-databases/performance/query-profiling-infrastructure.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -190,6 +190,9 @@ For more information on the performance overhead of query profiling, see the blo
190190
> [!NOTE]
191191
> Extended Events that leverage lightweight profiling will use information from standard profiling in case the standard profiling infrastructure is already enabled. For example, an extended event session using `query_post_execution_showplan` is running, and another session using `query_post_execution_plan_profile` is started. The second session will still use information from standard profiling.
192192
193+
> [!NOTE]
194+
> On [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)], Lightweight Profiling is off by default but is activated when an XEvent trace relying on `query_post_execution_plan_profile` is started, and is then deactivated again when the trace is stopped. As a consequence, if Xevent traces based on `query_post_execution_plan_profile` are frequently started and stopped on a [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] instance, it is strongly advised to activate Lightweight Profiling at global level with traceflag 7412 to avoid the repeated activation/deactivation overhead.
195+
193196
## See Also
194197
[Monitor and Tune for Performance](../../relational-databases/performance/monitor-and-tune-for-performance.md)
195198
[Performance Monitoring and Tuning Tools](../../relational-databases/performance/performance-monitoring-and-tuning-tools.md)

0 commit comments

Comments
 (0)