# Data Stores

The **Data Stores** page in Platform Settings allows administrators to configure and manage connections to external databases used by Nexus for storing time-series and event data.

Currently, Nexus supports data stores of type **KQL Database (Azure Data Explorer)**. These data stores serve as the primary backends for collecting and querying production, operational, and machine data captured through devices.

By configuring one or more data stores, organizations can ensure flexibility in how and where their data is persisted, making it possible to connect Nexus with enterprise-grade Azure-hosted data services.

These settings require the [Administrator Role](../../platform-architecture/security-architecture/user-roles-and-permissions) to access and modify.

***

## Key Capabilities

* **Centralized Data Configuration**\
  Manage all your data store connections in one place under Platform Settings.
* **Support for KQL Databases**\
  Connect Nexus directly with to [**Azure Data Explorer (ADX)**](https://azure.microsoft.com/en-us/products/data-explorer) database **,** or [**Microsoft Fabric KQL database**](https://learn.microsoft.com/en-us/fabric/real-time-intelligence/create-database) for advanced time-series analytics.
* **Default Data Store**\
  Define a default data store that is automatically assigned whenever new [asset hierarchies](../designer/assets/asset-hierarchies) are created. This ensures consistent data collection without requiring additional setup each time.
* **Multiple Stores**\
  Configure and switch between different stores for testing, production, or specialized workloads. Each Site may have its own datastore to enable seperation of data, and better control of who has access to data.

***

### Using Data Stores in Nexus

* **Asset Hierarchies Integration**\
  All configured data stores can be referenced by asset hierarchies, allowing real-time and historical data from devices to be stored and queried.
* **Default Store Behavior**\
  The data store marked as _Default_ is preselected whenever a new hierarchy is created. Administrators can later change the target store if necessary.
* **Flexibility Across Environments**\
  Use separate stores for development, testing, and production to manage data independently across environments.

***

## Key Configurations

<figure><img src="https://570593659-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYMGRODsc2QD3N3wmfwTl%2Fuploads%2FthD71E4P6IC4kHn3vrhf%2Fimage.png?alt=media&#x26;token=6851242b-55a0-4314-aef2-2142773b0053" alt=""><figcaption><p>Data Stores of Platform Settings</p></figcaption></figure>

The **Data Stores** tab displays a list of all configured data stores with the following details:

* **Name** – The user-defined name of the store.
* **Host Address** – The connection address (e.g., cluster endpoint for Azure Data Explorer or MS Fabric  endpoint).
* **Database** – The target database inside the data store. This is the database where data is send to and retrieved from.
* **Type** – Currently, only _KQL Databases (Data Explorer)_ is supported.
* **Default** – Indicates which store is marked as the platform’s default.

***

### Adding a New Data Store

<figure><img src="https://570593659-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYMGRODsc2QD3N3wmfwTl%2Fuploads%2FByFEYAo6WqsnK2yG2lbU%2Fimage.png?alt=media&#x26;token=29164e01-a670-4d86-b1b2-2a1c843650f6" alt=""><figcaption><p>Add new Datastore Window</p></figcaption></figure>

To add a new data store:

1. Select **Add**.
2. Provide the required fields:
   * **Name** – Friendly name for identifying the store.
   * **Host Address** – The URL of the Azure Data Explorer Cluster or [Ingestion URL of a KQL Database hosted in MS Fabric](https://learn.microsoft.com/en-us/fabric/real-time-intelligence/access-database-copy-uri).
   * **Type** – Select _Azure Data Explorer_.
   * **Database** – Name of the database to be used (this is case-sensitive)
   * **Tenant ID** – Azure Active Directory tenant.
   * **Client ID** – Registered application ID in Azure AD.
   * **Client Secret** – Secret key for authentication.
3. Save the configuration.

Once added, the data store becomes available for use in asset hierarchies.

***

### Managing Data Stores

* **Edit** – Update details such as database, credentials, or host address.
* **Delete** – Remove a store that is no longer required (ensure that no active hierarchies depend on it).
* **Set Default** – Define the store that will be used by default for new hierarchies.
