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

# Edit the Database Parameters

> Change the Application Server's database type, authentication method, encryption, and binary data storage location after installation.

<Warning>
  **NOT AVAILABLE IN SAAS.**
</Warning>

The database connection settings defined when Syteca Application Server was installed can be changed afterward using the **Syteca Server** tray application's **Database Parameters** tool (`DbSetupToolUI`).

<Steps>
  <Step title="Open the Database Parameters tool">
    Right-click the [Syteca Server tray icon](/docs/administration/deployment/server-tray-application) in the Windows notification area and select **Database Parameters**.
  </Step>

  <Step title="Set the database connection">
    On the **Metadata Storage** sub-tab, configure:

    * **Database Type** — the database engine to use for storing data.

          <Note>
            Switching database types doesn't migrate existing data.
          </Note>

    * **Host Name** — the hostname or IP address of the database server.

    * **Authentication** *(MS SQL Server only)* — one of:

      * **SQL Server Authentication** — enter the SQL Server **User Name** and **Password**.
      * **Windows Authentication** — enter the user as `<domain>\<user>` or `<user>@<domain>`, or click **Browse** to select one.
      * **Use process credentials** — for [gMSA/sMSA accounts](/docs/administration/database/gmsa-account) or to work around [NTLM authentication errors](/docs/administration/database/windows-authentication-ntlm) with Windows Authentication.

          <Note>
            The database user specified must have `db_ddladmin`, `db_datareader`, `db_datawriter`, and `db_executor` permissions on the SQL database.
          </Note>

    * **Use encrypted connection** — enables SSL encryption between the Application Server and the database.

          <Note>
            Requires a database server certificate configured beforehand and imported as a trusted certificate on this computer.
          </Note>
  </Step>

  <Step title="Choose where binary data is stored">
    On the **Binary Data Storage** sub-tab, select one option:

    | Option                     | Recommended for              | Notes                                                                                                                                                                                                                                                                       |
    | -------------------------- | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | **SQL Database**           | Small deployments only       | All monitoring data received from Clients is stored on the SQL server's computer.                                                                                                                                                                                           |
    | **File System**            | Medium and large deployments | Stores binary data in a shared or local folder. Shared folder format: `\\<computer_IP_address>\<folder_path>` or `\\<computer_name>\<path_to_folder>` (for example `\\admin-pc\SharedFolder`). Local folder format: `<path_to_folder>` (for example `C:\BinaryDataFolder`). |
    | **Amazon S3-like storage** | Medium and large deployments | Stores binary data in an existing Amazon S3 location. See [Configure Syteca to store binary data in Amazon S3](/docs/administration/database/binary-storage-s3) for the parameters this requires.                                                                                |

    <Note>
      If the File System folder becomes inaccessible, monitoring data is written to the local cache instead, and sent automatically once the folder is reachable again. Check the [System Health](/docs/administration/dashboards/system-health-dashboards) page for related error events.
    </Note>
  </Step>

  <Step title="Apply the changes">
    Click **OK**. If using Windows Authentication, you'll be prompted to validate the database logon for the current Windows user running the Database Parameters tool — this succeeds only if the Application Server is also running as that same user.
  </Step>

  <Step title="Restart the Application Server">
    Restart the **EkranServer** service to apply the changes.
  </Step>
</Steps>

<Frame caption="The Database Parameters (DbSetupToolUI) tool's Metadata Storage sub-tab.">
  <img src="https://mintcdn.com/syteca/0FlD-vkHsBA1azVX/images/administration/database/database-parameters-metadata-storage.png?fit=max&auto=format&n=0FlD-vkHsBA1azVX&q=85&s=79eadbf1f02da894bd22915c795f08c4" alt="Database Parameters tool showing database type, host name, and authentication fields" width="560" height="556" data-path="images/administration/database/database-parameters-metadata-storage.png" />
</Frame>

## Related

<CardGroup cols={2}>
  <Card title="Database management" icon="database" href="/docs/administration/deployment/database-management">
    Archive, cleanup, and PostgreSQL maintenance settings.
  </Card>

  <Card title="Amazon S3 binary storage" icon="cloud" href="/docs/administration/database/binary-storage-s3">
    Store binary session data in Amazon S3 instead of the file system.
  </Card>

  <Card title="System Health dashboards" icon="activity" href="/docs/administration/dashboards/system-health-dashboards">
    Monitor database connectivity and error events.
  </Card>

  <Card title="High availability" icon="server" href="/docs/administration/deployment/high-availability">
    Database considerations for multi-server deployments.
  </Card>
</CardGroup>