Waiting for Results
Users are patient, up to a
point.  You need a solid
plan to fix those reports.
Here are some keys to success:
  • Build a Foundation:  Pre-calculate
    key metrics and store the values in
    central tables for reports to use.
  • Data Mart ETL:  To avoid high
    daytime DB contention, process
    data into static tables at night.
  • Data Dictionary:  Write it down,
    create standards, and add source
    control to keep it clean over time.
  • Upgrade SQL Skills:  Make sure
    business users and IT staff know
    how to write efficient SQL.
Related Info

Which metrics appear in multiple reports? These key values should be calculated once per update cycle and stored in one place.

Reports can pull values from the central location, solving three issues: Erratic Results, Slow Response, and Random Deadlocks.

Identifying key metrics and setting up foundational tables isn't hard, but some analysis is required. The goal is to get rid of duplicate code.

Data Mart ETL

Implementing Data Mart ETL for reporting and analysis involves more than just updating code. It's a shift in mindset, as well.

If you're just starting out with Data Mart ETL, it's worth investing time up front to make sure everyone understands the benefits.

For details, read my post:
Data Mart ETL Basics