From 57fc929545135503d2042274d918c92aa85d4607 Mon Sep 17 00:00:00 2001
From: LorraineBigmore <64900936+LorraineBigmore@users.noreply.github.com>
Date: Thu, 27 Oct 2022 18:21:17 +0100
Subject: [PATCH] Update intelligent-query-processing-details.md

Making update as requested by Ling Duan on 2022-10-25 as a result of investigation of ICM 341205385 https://portal.microsofticm.com/imp/v3/incidents/details/341205385/home
Which resulted in defect hotfix 2046472  https://msdata.visualstudio.com/Database%20Systems/_workitems/edit/2046472
The result of the hotfix will be the query hint optimize for parameter may not be eligible for interleaved execution
---
 .../performance/intelligent-query-processing-details.md         | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/relational-databases/performance/intelligent-query-processing-details.md b/docs/relational-databases/performance/intelligent-query-processing-details.md
index 96a4d598b70..3a6a0142a5a 100644
--- a/docs/relational-databases/performance/intelligent-query-processing-details.md
+++ b/docs/relational-databases/performance/intelligent-query-processing-details.md
@@ -74,6 +74,8 @@ Contrast the prior plan with the actual plan generated with interleaved executio
 
 MSTVF referencing statements in interleaved execution must currently be read-only and not part of a data modification operation. Also, MSTVFs are not eligible for interleaved execution if they do not use runtime constants.
 
+Using the query hint `OPTIMIZE FOR` parameters may not be eligible for interleaved execution and could disable the feature for the query.
+
 ### Interleaved execution benefits
 
 In general, the higher the skew between the estimated vs. actual number of rows, coupled with the number of downstream plan operations, the greater the performance impact.