Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 4 · BI Publisher: data models, templates and bursting
Performance: making a slow report fast
Lesson 39 of 177 · 2 min
Time is almost never spent where people look first. The instinct is to blame the template; the answer is usually the query, and occasionally it is neither. Measure before you change anything. Run the data model alone and note how long it takes and how many rows it returns. That single number splits the problem in two: if the query is slow, the template is irrelevant; if the query is fast and the report is slow, the rows or the layout are the cause. The fix order that works. One: ROW COUNT. A report returning two million rows to render forty pages is doing the work twice; filter in the query, not in the template. Two: THE QUERY PLAN — a function wrapped around a filtered column, a join with no index behind it, a subquery evaluated per row. Three: TEMPLATE COMPLEXITY, which matters at volume: nested conditions evaluated per…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 4 · BI Publisher: data models, templates and bursting
- 1What a data model actually isFree preview
- 2SQL data sets: writing the query
- 3Parameters and lists of values
- 4Bursting: one run, many recipients
- 5RTF templates: the practical subset
- 6Excel and eText templates
- 7Sub-templates and reuse
- 8Layout, pagination and the printed page
- 9Localisation: Arabic, dates and numbers
- 10Performance: making a slow report fast
- 11Security in BI Publisher
- 12Scheduling and delivery
- 13What breaks: five BI Publisher failures
- 14Lab briefing · A supplier statement, end to end