AMRIT
  • Introduction
  • Architecture
    • System architecture overview
    • API Guide
    • Integrations
  • Developer Guide
    • Codebase structure
    • Development environment setup
      • System Requirements
      • Software dependencies
      • Installation Instructions
        • For UI repositories
        • For API repositories
      • Common Issues and Troubleshooting
  • Deployment
    • Installation guide
    • CI/CD pipelines
    • Observability
    • Wildfly
      • SSL Configuration for WildFly
  • Data Management
    • Database schema
    • Data privacy and security
    • Data export
    • Reporting
      • Integrating DHIS2 with AMRIT
      • Example Python Scripts
  • Community and Support
    • Contributing to AMRIT
    • How to get help
    • Code of conduct
    • Contribution guidelines
Powered by GitBook
On this page
  1. Data Management

Data export

PreviousData privacy and securityNextReporting

Last updated 5 months ago

Reporting Database

The AMRIT Platform includes a dedicated Reporting Database(db_reporting) designed to handle all reporting-related data. This separation ensures that operational data and reporting queries do not interfere with each other, enhancing performance and reliability for both real-time operations and analytical tasks.

Replication Database for High-Load Queries

For executing high-load queries for reporting or analytics, the AMRIT Platform recommends setting up a Replication Database. This database replicates the main transactional database and serves as a read-only source for heavy queries. By offloading such queries to the replicated database, the main transactional database can focus on application read/write operations without performance degradation.

For a detailed explanation of tables, relationships, and database schemas across different service lines (HWC, Scheduler, Inventory, etc.), refer to the

AMRIT Database Schema Documentation.