Solutions > Business Intelligence > Reporting Database

Workload Distribution

HVR can replicate into a data warehouse or a reporting database. Regular users will use the production database, whereas the reporting database will be used for reporting and analytical purposes. This means that end user performance is not affected by reporting and reporting is not interrupted by end user locks. The target database for workload distribution could be the same DBMS as the production database, or it could be a different DBMS, e.g. reporting tools may run better on a Microsoft SQL Server database.

Often reports query into SQL Views. When these Views are complicated and the database is large, then the reports can run slowly because of the extra runtime joins. HVR offers the ability to run the reports against the Materialized Reporting Tables, instead of the SQL Reporting Tables Reporting Views. These Materialized Reporting Tables contain the same data as the Views, but they are real tables instead. When HVR replicates changes to the user tables, it also changes the data in the Materialized Reporting Tables. This makes reports run faster.

Reporting Database as Standby Database

Most companies have mission critical database applications. HVR can protect these systems by continuously replicating to a standby database, e.g. the reporting database. Operation can be switched to the standby database at any time; either in an emergency or perhaps just every night to avoid planned downtime. The standby database does not have to be in the same building. HVR’s extreme efficiency over the network means it can easily be located over the WAN. This reduces the risk that an emergency which affects the main database will also affect the standby.