> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Other Databases

> GermainUX supports Elasticsearch, PostgreSQL, MySQL, Oracle Database, and Microsoft SQL Server.

Service
`Enterprise`

Availability
2024-01-01

> **[Support for Additional Datastores](#support-for-additional-datastores)**
>
> Which databases are supported

> **[Request an Assessment](#request-an-assessment)**
>
> What to send for review

> **[Integration Process](#integration-process)**
>
> Steps to add a database

> **[Considerations](#considerations)**
>
> Performance and fit tradeoffs

## Support for Additional Datastores

GermainUX supports Elasticsearch, PostgreSQL, MySQL, Oracle Database, and Microsoft SQL Server. Elasticsearch is the preferred datastore for most new and high-volume deployments.

Support for another database technology may be added when required by your organization.

Integrating a new datastore typically requires at least one week of engineering work. The actual timeline depends on:

* Database technology and version
* JDBC or API compatibility
* SQL syntax and data types
* Indexing and partitioning capabilities
* Transaction behavior
* Ingestion performance

> **Show all 12**
>
> * Analytical-query support
> * Retention and cleanup mechanisms
> * Schema-generation requirements
> * Migration requirements
> * Security and authentication
> * Testing and certification

## Request an Assessment

To evaluate another database, provide:

* Database product and exact version
* Deployment model: on-premise, managed cloud, or clustered
* Operating system
* JDBC driver or supported API
* Authentication and encryption requirements
* Expected daily AA Unit volume

> **Show all 14**
>
> * Peak ingestion rate
> * Expected retained-data volume
> * Raw and aggregated retention periods
> * Session Replay requirements
> * High-availability architecture
> * Backup and disaster-recovery requirements
> * Required implementation date
> * Development or test environment availability

Germain Software will assess compatibility, required engineering effort, performance risks, and the expected delivery timeline.

## Integration Process

A typical new-database integration includes:

* Review database capabilities and limitations.
* Confirm connectivity and driver compatibility.
* Map GermainUX data types and schemas.
* Adapt database-creation and upgrade scripts.
* Implement query and persistence support.
* Configure retention and data cleanup.

> **Show all 11**
>
> * Test ingestion and analytical queries.
> * Benchmark representative data volume.
> * Validate upgrades, backups, and recovery.
> * Document installation and maintenance.
> * Certify the supported database version.

Production support is confirmed only after the integration and validation have been completed.

## Considerations

A technically compatible database may still be unsuitable if it cannot efficiently support GermainUX’s:

* Near-real-time ingestion
* Large monitoring datasets
* Time-based retention
* Aggregations
* Percentiles and statistical analysis
* Search and filtering

> **Show all 10**
>
> * Concurrent dashboards
> * Root-cause analysis
> * Session Replay metadata
> * Required production scale

When no organizational requirement mandates another database, use [Elasticsearch](/main/elasticsearch-database-preferred.md).

To request support for an additional datastore, [contact Germain](/main/support.md) team.

## Get Help

> **[Contact GermainUX Support](/main/support.md)**
>
> The Germain Team can help you set this up.

> **Can't find what you need?**
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.