Understanding OpenSimulator databases
Detailed OpenSimulator 0.9.3.1 explanations based on INI templates and source code.
A grid does not necessarily have one database
In 0.9.3.1 each ROBUST or simulator process reads its own configuration. Multiple schemas on one MySQL server, one shared schema, or different SQL servers are possible. Region count does not determine database count.
ROBUST and central services
ROBUST typically runs accounts, authentication, inventory, assets, friends, presence and grid-region directory services. GridStore holds region directory records, not scenes. Optional add-ons may use further databases.
Scene persistence
A simulator persists objects, parcels, terrain and region settings through a provider such as MySQLSimulationData and RegionStore tables. Several regions can share those tables, with RegionUUID distinguishing records.
Estates
EstateStore contains estate settings, owners, managers, restrictions and region-to-estate mappings. It can use the simulator connection, a dedicated EstateConnectionString or an explicitly configured central ROBUST service.
FSAssets and separate data layers
FSAssets metadata and asset files do not replace RegionStore scene records. Moving assets to a dedicated disk does not move region or estate databases.
Simplified logical diagram: real connections depend on your INI settings.
ROBUST -> [DatabaseService] -> SQL services centraux / central services SIMULATEUR -> [DatabaseService] -> SQL RegionStore / scenes ESTATES -> connexion locale / EstateConnectionString / ROBUST distant Un même schéma peut réunir plusieurs fonctions. One SQL schema can serve several roles.
Other guides in this section
- INI files and SQL connections
- Regions.ini and region tables
- OpenSim.ini, Estates.ini and estate storage
- OpenSimulator 0.9.3.1 SQL tables
- Backing up and migrating OpenSimulator databases
- Administer MySQL / MariaDB
- Install a ROBUST grid
- Understanding FSAssets