Correct severe misconception about SetCurrentKey in the knowledge base - #135
Merged
Conversation
dcenic
requested review from
Bardur Knudsen (BardurKnudsen) and
Bugsy (pchriste-microsoft-com)
as code owners
August 22, 2026 10:07
Bardur Knudsen (BardurKnudsen)
approved these changes
Aug 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A common misconception is that
SetCurrentKeytells SQL Server which index to use for a query. It does not. In Business Central,SetCurrentKeyonly changes theORDER BYclause of the generated SQL statement. It does not add an index hint, and the SQL Server query optimizer is free to ignore the named key entirely.We must therefore fix this knowledge base article and stop asking AL developers to use SetCurrentKey blindly. If you genuinely don't need sorting of the result set, it is detrimental - it hurts your performance and doesn't provide any hint to SQL Server.