Breadcrumbs

Configuring External SQL Database

Overview

By default, Login Enterprise is delivered using an internal database. However, you can add an external SQL database.

Important: Before you choose to migrate to an external SQL database in Login Enterprise, there are several things you need to consider:

  • Migrating to an external SQL database is a one-way process. If you choose to go back to the internal database, your data will not be transferred back into the internal database and you will have data loss.

  • Migrating to an external SQL database will result in deleting all existing data collected up to that point.

If you choose to migrate to an external SQL database, please create a snapshot to eliminate the possibility of losing data permanently.

Why Use an External SQL Database?

Benefit

Explanation

Improved scalability

Enables Login Enterprise to handle increased data volumes and user loads more efficiently.

Centralized management

Allows database administrators to monitor and optimize the database independently for better control and maintenance.

High availability and redundancy

Provides built-in features that ensure the system remains operational and resilient to failures.

Enhanced security

Offers advanced security measures to better protect data and maintain integrity.

Better performance

Improves overall system efficiency compared to internal database setups.

Integration flexibility

Supports seamless integration with various platforms and applications.

Easier compliance

Simplifies meeting regulatory and compliance requirements.

Long-term efficiency

Contributes to sustainable performance and reliability as Login Enterprise grows.

External SQL Database Requirements

For the successful external SQL database implementation in the Login Enterprise user interface, there are several requirements:

  1. Login Enterprise is compatible with Microsoft SQL Server 2016, 2017, 2019, and 2022.

  2. A database must exist on the SQL Server instance.

  3. The SQL database connection requires an SQL user, not a Domain User.

  4. Ensure that Named Pipes are enabled for the SQL Server service

  5. The connection can be configured to utilize SSL when communicating with the SQL Server.

The minimum requirement for external SQL is the same as the default size of the Appliance or the minimum requirement for the version of the SQL you choose, whichever is greater.

Appliance Default:

Configuration

CPU

Memory

Disk

Recommended

4(v)CPU

8GB RAM

100GB

Configuring an External SQL Database

To configure the external SQL database in the Login Enterprise user interface:

  1. In the Login Enterprise sidebar menu, navigate to Other > System.

Frame 1980.png

  1. In System, select Database configuration from the tab menu.

Frame 1993.png

  1. In Database configuration, provide the following details:

Field

Definition

Database server hostname

Hostname / IP / FQDN of SQL server.

Database server port number

The port number used to communicate with the SQL server

SSL/TLS settings

  • Select Enable SSL to enhance the security of your connection by encrypting the data exchanged between the appliance and the SQL server. This is the recommended choice to protect sensitive information during transmission.

  • Select Ignore SSL errors to allow the connection to proceed even if there are SSL-related issues.

Database instance name

The name of the preferred instance for the database configuration.

Database name

The name of the created database.

Username

The username of the preferred SQL user.

Password

The password of the SQL user.
Frame 1994.png

  1. Click Test connection to ensure the database is correctly configured.

  2. Click Apply DB config to save the database configurations.

Congratulations, your external SQL database has now been configured.