Skip to Main Content
Sage 200 Evolution ZA Ideas Portal

Welcome to the Sage 200 Evolution ideas Portal

Created by Guest
Created on Nov 10, 2025

Change to the way the program calls the SQL

When trying to print, we get this error:

When I do a SQL profiler query to see what the issue is, I see that the issue is on the following query:

On research I see that OPTION (QUERYTRACEON 9481) is an old system call that shouldn’t really be used by the application, the correct query is to write “OPTION (USE HINT ('FORCE_LEGACY_CARDINALITY_ESTIMATION'))” as this is the new and correct way that does not require SysAdmin role.

If I give the SQL Evo user SysAdmin roles then there is no issue and the printing works fine, however giving a SQL user that is used by an application SysAdmin is highly irregular and not advisable in terms of security.

When I try and find the stored procedure or function that writes the “OPTION (QUERYTRACEON 9481)” I cannot find this in the database and so it must be written as code in the application.

If I look on Sage there is a Solution ID to this problem in 2020 but when I try find it using the Solution ID as recommended on Sage it cannot be found.

SOLUTION ID

ARTICLE TITLE

PUBLISHED DATE

200512050242266

Inventory, Order Entry, Job Costing, POS: 'Error initialising report data! Reason: User ¦¦does not have permission to run DBCC TRACEON

05/12/2020

Thanks

Harry

Nicholas Harrison (Harry)

What is the workaround for the problem today?

Gave EvoConnect user SysAdmin rights

Your Designation/Role Customers Services
Email.
  • Attach files