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

# What is a database

> Learn what a database is in Oculon and how databases support models, analysis, and reporting.

A database in Oculon stores structured records that can be reviewed directly or used as source data across models, views, and boards. It gives you a stable place to manage operational data without rebuilding that data inside each model.

![Database detail view in Oculon showing structured source records](https://mintcdn.com/oculon/VPBn_Cv6-GOeV3l9/images/getting-started/fr-db.png?fit=max\&auto=format\&n=VPBn_Cv6-GOeV3l9\&q=85\&s=140b40f8f1288d5e3dc8e96d077795de)

## Why databases matter

Databases help you:

* centralize source records
* keep raw data separate from planning logic
* refresh data from integrations and queries
* reuse the same source data across several downstream workflows
* reduce manual re-entry when multiple teams rely on the same records

## Where databases fit in Oculon

Think of databases as the source layer in the Oculon workflow:

* `Databases` hold source records and imported data.
* `Models` apply calculations, assumptions, and planning logic.
* `Views` and `Boards` help teams review the result.

This separation matters because source data and planning logic usually need different owners and different change controls.

## Common ways to create a database

The current Oculon docs show two common creation paths:

* `Manual database`: create and manage the structure directly in Oculon
* `Query-backed database`: create a database from an integration query so the source can refresh over time

Both approaches create a database that can later support models, reporting, and review workflows.

## Database versus model

Use a database when you need row-level records, imported source data, or operational detail.

Use a model when you need:

* calculations and formulas
* scenarios and planning assumptions
* time-aware logic
* outputs designed for planning and decision-making

A database gives the model a clean starting point. The model gives the database business meaning.

## What databases usually feed

A well-structured database can later feed:

* model inputs
* dimension mappings
* linked records and shared reporting inputs
* board tables and supporting analysis

This is why structure decisions inside a database often matter outside the database itself.

## Related pages

* [Database types](https://oculon.mintlify.site/docs-new/databases/database-types.md)
* [Database structure](https://oculon.mintlify.site/docs-new/databases/database-structure.md)
* [Working with data](https://oculon.mintlify.site/docs-new/databases/working-with-data.md)
* [Linked data](https://oculon.mintlify.site/docs-new/databases/linked-data.md)
* [Core concepts overview](https://oculon.mintlify.site/docs-new/getting-started/core-concepts-overview.md)


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