QueryLogJobDefinition may be exhausting the SQL connection pool

Hi Colotta Jerrae

As far as I know, at the moment, Microsoft has not published an official known issue specific to KB5002843 that directly addresses this behavior.

However, this pattern closely matches a previously known issue where the Search Query Logging timer job did not consistently release SQL connections, eventually exhausting the SQL connection pool over time.

However, the following approaches can help you reduce the impact:

• As a temporary mitigation, restarting the SharePoint Timer Service (SPTimerV4) on a scheduled basis can help clear stale SQL connections and prevent prolonged search failures.
• If search query analytics are not critical for your organization, disabling the Search Query Logging timer job is an effective way to prevent further SQL pool exhaustion.
• Increasing the SQL connection pool size may delay the issue, but it should be treated as a short-term mitigation rather than a long-term solution if a connection leak is present.

Additionally, based on current information, there is no clear indication that these Hybrid Search changes directly cause the SQL connection pool exhaustion observed with QueryLogJobDefinition.

Hope my answer will help you, for any further concern, kindly let me know in the comment section.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.