web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

How to control AL data retrieval behavior to avoid automatic FAST 50 injection in Business Central?

(2) ShareShare
ReportReport
Posted on by 6

I am facing a severe performance issue where Business Central (tested on v24 and v27) automatically injects the OPTION (FAST 50) hint into all SQL queries.

This is causing a "low memory grant" problem: the SQL Optimizer estimates a tiny memory requirement based on 50 rows estimation. When the query actually processes thousands of records, it results in massive TempDB spills and I/O pressure across the entire instance.

I mainly use the FindSet and Find function in AL, but I haven't found any documentation or parameters for this function that would allow me to control or disable this hint. I want to avoid manually managing Plan Guides or forcing plans in Query Store for every single case.

Is there a specific Business Central configuration that force the usage of the OPTION (FAST 50) hint ?

Thank you for any kind of help.

I have the same question (0)
  • Suggested answer
    YUN ZHU Profile Picture
    101,458 Super User 2026 Season 1 on at
    I haven't encountered this problem.
    You can report this issue to Microsoft.
     
    Alternatively, if you want a temporary solution, you might try using a query.
    Filtering in Query objects:
     
    Hope this helps.
    Thanks.
    ZHU
  • Gerardo Rentería García Profile Picture
    26,846 Most Valuable Professional on at

    Hi, good day
    I hope this can help you, and give you some hints.

    JIT loads vs Full record load

    Best Regards
    Gerardo

  • Suggested answer
    Assisted by AI
    OussamaSabbouh Profile Picture
    16,743 Super User 2026 Season 1 on at
    Hello,
    I don’t see any supported Business Central setting to disable or control OPTION (FAST 50): Microsoft documents only a few configurable SQL hints (FORCE ORDER, LOOP JOIN, OPTIMIZE FOR UNKNOWN), and for AL access it states FindSet reads the full set and is not a TOP X pattern, so FAST 50 appears to be internal platform SQL generation behavior, not something exposed in AL or server config; the practical fix is usually to revisit the data access pattern, keys, filters, and query shape rather than looking for a BC switch.
     
    Regards,
    Oussama Sabbouh

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,216 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,471 Super User 2026 Season 1

#3
AndrewThomas81 Profile Picture

AndrewThomas81 1,369

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans