-- FORCESCAN Hint added to force query optimizer to choose scan over seek
/* Often while tuning stored procedures, we will see tables have the "seek" operator.
Few times one of reason for slow performance is wrong estimates on number of rows.
Because of that, there are more chances that query optimizer choose "SEEK" over "SCAN".
To force optimizer to choose "SCAN" over "SEEK", FORCESCAN hint has been added. */
Select OH.OrderID,OD.ItemName,OH.OrderCost
from OrderHeader OH
INNER JOIN OrderDetails OD WITH (FORCESCAN)
on OH.OrderID = OD.OrderID
/* Often while tuning stored procedures, we will see tables have the "seek" operator.
Few times one of reason for slow performance is wrong estimates on number of rows.
Because of that, there are more chances that query optimizer choose "SEEK" over "SCAN".
To force optimizer to choose "SCAN" over "SEEK", FORCESCAN hint has been added. */
Select OH.OrderID,OD.ItemName,OH.OrderCost
from OrderHeader OH
INNER JOIN OrderDetails OD WITH (FORCESCAN)
on OH.OrderID = OD.OrderID
No comments:
Post a Comment