Skip to content

Commit e2b4319

Browse files
authored
Merge pull request ktaranov#220 from denver-ua/patch-1
Update SQL Server Trace Flag.md
2 parents d213bed + 5ea3f86 commit e2b4319

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

SQL Server Trace Flag.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4787,6 +4787,15 @@ Link: [New Undocumented Trace Flags]<br />
47874787
Scope: ?
47884788

47894789

4790+
<a id="9265"></a>
4791+
#### Trace Flag: 9265
4792+
**Undocumented trace flag**<br />
4793+
Function: MS engineering team has decided to generate a DUMP from SQL 2019+ every time a “PLAN cannot be generated”. Once a Dump freezes connections during the generation, the cluster will probably lost the connectivity to the cluster and the AG can be down/failover if it has automatic failover configured. The mitigation for this issue (avoid DUMP generation) is to enable TF Trace Flag 9265 on Startup.
4794+
Once TF 9265 is enabled, SQL Server stops generating DUMP on the “PLAN cannot be generated” error but only writes a message to ERRORLOG file (Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services).
4795+
<br />
4796+
Link: None
4797+
4798+
47904799
<a id="9268"></a>
47914800
#### Trace Flag: 9268
47924801
Function: SQL 8 - When SQL Server runs a parameterized query that contains several IN clauses, each with a large number of values, SQL Server may return the following error message after a minute or more of high CPU utilization: KB 325658. Server: Msg 8623, Level 16, State 1. Internal Query Processor Error: The query processor could not produce a query plan. Contact your primary support provider for more information.<br />

0 commit comments

Comments
 (0)