Reporting from transactional detail is the most flexible thing possible. But it also is the most expensive because of data volumes. Our approach has been to test if we could use transactional data to produce our reports. In Step 4 of estimating metric engine processes, we’ve determined that it is not possible. Reducing processing costs is possible with a posting processes. Posting processes eliminate unneeded … Continue reading Final Step: Aggregate or Post to Produce Reports

After performing some tests to determine run times for reports given a potential hardware environment (as described last week in Step 3), the next step is to evaluate the results. Remember, I’ve suggested that the ultimate in report flexibility comes from doing all reporting from transactional detail:  If we capture the attribute on the transaction, then we can use it in a report if we … Continue reading Step 4: Evaluate Performance of Reporting Process

Build an initial model of performance by bringing together the statistics gathered in steps 1 and 2 Continue reading Step 3: System Performance in Estimating Reporting Processes

Gather statistics about the reports to be produced. Continue reading Step 2: Report Characteristics in Estimating Reporting Processes

Gather statistics about business events (transactions), frequencies, and static or reference data to be needed for the reporting domain. Continue reading Step 1: Transactions needed for a Metric Engine