> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/workspace-and-data-management/connecting-to-a-database.md). # Connecting to a Database ## Databases GeoDin data is stored in databases, which may contain any number of GeoDin projects - the only limit is your disk space.\ Databases are accessed using a specialized database driver (OLE-DB-Provider). This driver is included in your operating system or is provided with your database. Database connections are created, configured or deleted from the GeoDin user interface. Depending on how the data is stored and managed, GeoDin differentiates between the following database types: **Desktop databases**\ \ GeoDin data is stored in a user-defined physical database format such as Microsoft-Access (MDB). In order to use a desktop database you need a database connection. This can be done directly in GeoDin. Any program that supports the database format can be used for viewing or editing the data. The database operations are performed on the client PC. \ **Client/Server databases**\ \ Data is stored in a database on a database server e.g. Oracle, SQL-Server etc. In addition to a database driver and database connection, client software for the relevant database is needed. A database administrator must set up user identification on the database server, which appears when the database is opened (login). The database functions are implemented on the database server reducing computing load on the client PC(s).Client/server databases can be used from ***GeoDinProfessional*** onwards.\ The GeoDin-System contains functions to copy or transfer data between database types. Hence it is possible to change the database format of a project after it has been created. ## Hierarchy and general rules GeoDin databases can be defined on two distinct levels. **System databases** are configured centrally for a GeoDin installation and are displayed to every user who starts GeoDin from that installation. This is especially useful in network installations with client/server databases, as the database configuration only has to be done once centrally. A system database connection is created with the method **"Create database connection"** on the system level (see **Configuration**); the connection information is saved as a `*.CON` file in the `CONFIG` folder of the GeoDin installation, which can be write-protected on a network share and managed by the system administrator. These connection files can be passed on by file, or configured once by an administrator and then made available to all users. Any database settings defined on the system level override all other database definitions with the same name. The **Import** method transfers system database connections from an existing legacy `GEODIN.INI` file automatically into the current format. After selecting a `GEODIN.INI`, the recognized database connections are displayed; set the check marks in front of the databases to transfer and confirm with **OK**. Each imported connection is saved as a `*.CON` file named after the selected display name. {% hint style="warning" %} From GeoDin 9 onwards, system databases configured in `GEODIN.INI` are no longer displayed in the GeoDin Object Manager. Use the **Import** method to migrate legacy `GEODIN.INI` connections to `*.CON` files. {% endhint %} **User databases** are created or defined locally using the method **"Create database connection"**. The settings are stored on the user's PC and are available to the user that created them. **Database connection name** Different user databases cannot have identical names. A database connection defined as a system database is used in preference to a user-defined database ## Create database connection The method **"Create database connection"** is available under the ![Databases](/files/bfjcNTu2ghN5Hk8gY3kj) **Databases** tab in the GeoDin object manager (GOM): Upon starting the method you may then choose, whether to use an Access database or create a connection to a database server (with *GeoDin Client/Server* module). Since GeoDin 9, database connections are no longer created with OLE-DB, but exclusively with FireDAC. FireDAC has three main advantages over OLE-DB: 1. The connection allows faster access (especially noticable with client/server databases). 2. A complicated configuration process is not necessary (which is the case with ODBC connections). 3. The correlation of DLL\_ names of field type descriptors for Client/Server databases in the GeoDin.INI is not necessary. Detailed descriptions on FireDAC connections can be found here: The creation of database connections to Access databases is described in chapter: [MS Access](/workspace-and-data-management/connecting-to-a-database/supported-database-types.md) The creation of database connections to Client/Server databases is described in chapter: [Client/Server](/workspace-and-data-management/connecting-to-a-database.md) Object, measurement, report, document, and project-copy reference content formerly duplicated on this page now lives on its subject pages - see [Working with Measurement Data](/workspace-and-data-management/working-with-measurement-data.md), [Object Operations Reference](/object-types/object-operations-reference.md), [Working with Projects](/workspace-and-data-management/working-with-projects.md), [Report Templates](/visualization-layouts-and-reporting/report-templates.md), and [Managing Documents](/workspace-and-data-management/managing-documents.md). ## Related topics * [Managing Database Connections](/workspace-and-data-management/connecting-to-a-database/managing-database-connections.md) - editing, deleting, system vs. user databases, configuration * [Supported Database Types](/workspace-and-data-management/connecting-to-a-database/supported-database-types.md) - Access, SQL-Server, Oracle, MySQL, PostgreSQL specifics --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.geodin.com/workspace-and-data-management/connecting-to-a-database.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.