By using this website, you agree to our Terms of Use (click here)
My dba's tried turning this option on and we received the following errors. Since this is ran at the instance level and not db level, it captures all the queries ran on the instance for future analysis .
There are problems on database server side:
- There is a database object of type 'U ' named [QueryOptionGroup] in a different schema [msqta].
- There is a database object of type 'U ' named [TuningSession] in a different schema [msqta].
- There is a database object of type 'U ' named [ExecutionStat] in a different schema [msqta].
- There is a database object of type 'U ' named [MetaData] in a different schema [msqta].
- There is a database object of type 'U ' named [TuningQuery] in a different schema [msqta].
- There is a database object of type 'U ' named [TuningSession_TuningQuery] in a different schema [msqta].
Has anybody tried this yet? If we change the object type it might work, but i am looking to see if anyone has encountered this yet?
Got a answer back from my VAR, who got it from Acumatica...
After reviewing it into more details, the system checks for tables having different schemas other than dbo and report such errors.
Could you change the schema on these tables to dbo instead and test? ( it might break the Query Store)
We did a test and it does seem to allow the Query Store to run properly.
The VAR did ask
you could use Request Profiler and see the queries being run as well
But the Query Store is at the Instance level not the db level, so the dba's can see the entire instance at once and see contention issues.
Interesting, so install Query Store (click here), then change the schema on the tables that it creates to "dbo"?
It's funny, I haven't looked at SQL stuff in a long time since most of the Acumatica clients that I work with are using Acumatica SaaS where you don't have access to the database.
Online Members
