BAQ execution timeout expired

[Tripb44 (Kyle Vogt)]

I’m getting the below error on a baq. I’ve tried adjusting the timeout and still will get this error. Any ideas?

[jkane (John Kane)]

It is probably a bad join or going against too large of a table. We would need more info about the BAQ before we could offer a good solution.

[RaymondHianjaya]

Hi Kyle,

You can set 0 for time out in SSMS

Best Regards,
Raymond Hianjaya

[Jason_Woods]

@RaymondHianjaya

You can set 0 for time out in SSMS

Be careful. This may allow the query to work, but you will be allowing a potentially bad query to run without being fixed. This can eat up your CPU and RAM…

[rnewell (Ron Newell)]

You could also try increasing the query time out in the BAQ. Under actions menu select Execution Settings. Add the QueryTimeOut parameter, 600 was recommended to us and it works well whenever we run into thi

s error.

[mikelyndersOKCC (Mike Lynders)]

I had this problem and solved it by adding some additional criteria. For example, if your query can be limited to a single “Company” make sure the tables use the “Company” field in all joins and set a criteria on at least one table. The query engine might be able to optimize more if you give it a little more info.

[cfinley (Chance Finley)]

RDD BAQ Report timeout

This suggestion ultimately solved the problem of the long Query runtime. BAQ with date range of 06/01/2020 - 06/30/2020. 25 records that represent all the days we shipped something. With 8 inline subquery calculated fields. Run without any company criteria. Non Cross Company BAQ 13.683 minutes Run with company hardcoded company = ‘abcdef’ on all tables marked with 1 including inline subqueries 3.45 minutes Run with BAQ Special Constant of CurComp on all tables marked with a 1 including inl…

If you check out the thread within the thread, there is a discussion about problems with the BAQ Engine in all versions prior to version 10.2.700. Weird performance results throughout users experiences

[Jason_Woods]

@mikelyndersOKCC

For example, if your query can be limited to a single “Company” make sure the tables use the “Company” field in all joins and set a criteria on at least one table.

This is not actually true. You should ALWAYS join tables using the Company field. It is part of the index and will benefit your queries performance. If you only need one company, then filter by that company. If you are only one Company, still join by that field.

[Hogardy (Pierre Hogue)]

For us, we only have one company, but we still specify Company = BAQ CurrentCompany constant at the first table we add…That has resolved a few timeouts we had after our upgrade.

Pierre

[Joseph_Martin]

You can export a sql execution plan from the BAQ designer also, and view it in SSMS. That will show the costs of each part of your query, makes it easier to track down.

[Yodelayheewho (14)]

Your suggestion worked for me. Curious on why you selected ‘600’? I’m a newbee, so still learning the ropes. Thank you for your contribution!

[rnewell (Ron Newell)]

It was suggested by support, I have used larger numbers on some very large and slow BAQ’s but the 600 seems to work on most.

[Yodelayheewho (14)]

Thanks again!