Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 3 · The reporting stack: which tool answers which question
Performance, before you build
Lesson 27 of 177 · 2 min
The characteristics that make a report slow are decided at DESIGN, not tuned afterwards, and five minutes of questions before you write anything saves a week later. Ask about VOLUME first, and ask for a number. Not "a lot" — how many invoices a month, how many employees, how many years of history. A design that is comfortable at fifty thousand rows and impossible at five million looks identical on the day you build it. Ask about the DATE RANGE, and whether it is bounded. A report with no date filter is a report that gets slower every month it exists, and it will pass every test in the first year. Insist on a mandatory period parameter unless somebody can explain why the whole history is needed; that single constraint prevents more performance problems than any tuning. Ask what happens when a parameter is EMPTY. A parameter that means "all"…
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.