We have a report (version 4.1.3 of BO) that takes over 1 minute to “prepare” the SQL, while the query and results are returned in about 20 seconds. There is no message on what BO is doing to the end user while it appears to be generating the SQL. I have used BO Tracker and its only help is that the time delay is in the SQLBO module in the “Entering Prepare Function” . I get the same delay when I use the SQL syntax checker in BO. Any ideas on what is going on within the “Prepare Function”? Is there any documentation in general on the steps BO takes and what exactly is happening during all phases of the SQL generation, execution, and retreival?
We have a report (version 4.1.3 of BO) that takes over 1 minute to
“prepare” the SQL, while the query and results are returned in about 20 seconds.
I haven’t seen documentation but my experience is that the time after the results are returned and before they are presented, BO is “OLAPing” (to coin a term) the results. It’s sorting, aggregating, breaking, averaging, grouping, etc, the results to allow a faster return when you ask for changes in presentation. This would make it faster to pivot, slice and dice, drill down, etc. The bigger the result set, the longer it takes to prep it. That’s why you only use BO for OLAP when you’re dealing with “small” result sets. If you get into big sets with lots of analysis, go to a true OLAP solution and let BO query that instead.