BAQ - Linking PORel with TranGlc

[tsmith (Tyler Smith)]

Try removing the PORel.Company = TranGLC.Company join condition. There are other queries where having the Company condition causes the query to time-out, while removing it lets the query run in seconds. If the BAQ is not cross-company and not external, there should be no problem with removing the Company condition.

Improving BAQ Performance

The BAQ performance inconsistencies with adding or not adding the “Company = CurrComp” criteria, have been resolved with work done in 10.2.700. Prior to that work, the BAQ engine would automatically use a Temp Table it populated with valid Company values for the query and the TT would be “joined” to the Company column. Depending on what other criteria was in play, that join could result in sub-optimal performance. The BAQ has to account for a number of different scenarios including Cross Compan…

We have a fairly complex BAQ that looks at expenses and POs to budget and takes upwards of 20 minutes to run depending on the timeframe. I have it in my queue to test removing the company criteria to see if it improves performance.