Added explanation of what causes this and how to avoid it

[ghost]

No description provided.

[PRMerger6]

@greglow : Thanks for your contribution to the Azure documentation! The author, @MikeRayMSFT, has been notified to review your proposed change.

[MikeRayMSFT]

@greglow the recommendation (line 39) seems a little out of context in a topic specifically about an optimization option. Would this recommendation be more appropriate in the context of the Query Processing Architecture Guide?

[ghost]

Hi Mike The reason that this option exists at all is because of this issue. The article currently talks about how to apply the fix and what the option does, but it doesn’t tell you how to avoid getting into the situation in the first place. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: www.sqldownunder.com

…

________________________________ From: Mike Ray <notifications@github.com> Sent: Thursday, February 1, 2018 2:20:57 AM To: MicrosoftDocs/sql-docs Cc: Greg Low; Mention Subject: Re: [MicrosoftDocs/sql-docs] Added explanation of what causes this and how to avoid it (#394) @MikeRayMSFT requested changes on this pull request. @greglow<https://github.com/greglow> the recommendation (line 39) seems a little out of context in a topic specifically about an optimization option. Would this recommendation be more appropriate in the context of the Query Processing Architecture Guide<https://docs.microsoft.com/en-us/sql/relational-databases/query-processing-architecture-guide>? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#394 (review)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEkha8XUdy-77O00zXAt63wO-rWdL7rrks5tQK8JgaJpZM4Rx6oJ>.

[MikeRayMSFT]

@greglow - thank you for your contribution. #sign-off