How to Configure a Shared Local Database and Improve Performance Using SQL Server Across Multiple Brokers

How to Configure a Shared Local Database and Improve Performance Using SQL Server Across Multiple Brokers

Product: Thinfinity Workspace
Version: 7 and above


Thinfinity Workspace uses a shared local database based on Absolute Database, a Delphi database engine. It is a compact, fast, robust and easy-to-use database engine designed to improve performance and manage multiple functionalities. Access and authentication profiles, enterprise logging, notifications, resource reservations, VDI management, and identity provisioning are all centralized within this database. This setup ensures efficient data management and consistent operation across multiple brokers, optimizing user experience and system performance.

The purpose of this article is to guide users on how to configure a shared local database and improve performance across multiple primary brokers by detailing the configuration steps for SQL Server, Windows Firewall, and Thinfinity Workspace. For the purposes of this document, we will show the configuration using SQL Server, but you may use other database software.

I. Prerequisites

Before proceeding with the configuration, ensure you have:
  • Administrative access to all servers involved.
  • Thinfinity Workspace installed and accessible.
  • SQL Server installed and running.
  • SQL Server Management Studio installed.
  • New empty database created for use with Thinfinity Workspace.
Info
Note
Starting with Thinfinity Workspace 8.0.X, the product will be compatible with SQL ODBC Driver 18. Download the appropriate driver for the installed SQL version from Microsoft's website. The driver must then be added to ODBC Data Sources (either 64-bit or 32-bit, depending on the system).

II. Configuring SQL Server

Verify Remote Connections are Allowed

The first thing that you need to do is check that remote connections to the SQL Server are allowed. To do this, follow the steps:

1. Open SQL Server Management Studio (SSMS) by clicking START > Microsoft SQL Server > SQL Server Management Studio. Enter your password to connect.
2. Then right-click on the Server and select Properties.


3. In the Server Properties window select the Connections page on the left side of the window. In the right pane of the Server Properties window, ensure that Allow remote connections to this server is selected then click OK.


Set SQL Server Browser service Start Mode to Automatic

1. Start the SQL Server Configuration Manager. This can be found at the following location in the Windows Start menu Start > Microsoft SQL Server > SQL Server Configuration Manager.
2. In the SQL Server Configuration Manager dialog window select SQL Server Services. Start the SQL Server Browser service and check that the start mode is set to Automatic. This allows other computers to access the SQL server by IP or Server name.


Enable TCP/IP protocols for SQL Server Network Configuration

You will now enable TCP/IP to allow computers to connect to SQL Server over IP. To do that, follow the steps:

1. In the SQL Server Configuration Manager dialog window select SQL Server Network Configuration then right-click on TCP/IP and select Enable.
2. Similarly, enable Named Pipes to allow computers to connect to SQL Server using the server name: right-click Named Pipes and select Enable.

Alert
Note
You may need to restart the services for the changes to take effect.


3. The SQL configuration is now complete. You will now need to restart the SQL Server service. From the SQL Server Service on the SQL Server Configuration Manager, right-click the SQL Server and select Restart.


III. Configuring Windows Firewall

Create a new firewall rule that adds a program exception for the SQL Server executable

In order to do that, follow the steps:

1. From the Windows Start menu, type wf.msc and press Enter to open Windows Defender Firewall with Advanced Security.
2. In the left pane, select Inbound rules.
3. In the right pane, under Actions, select New rule. New Inbound Rule Wizard will open.


4. On Rule type, select Program then click Next.


5. Under Program, select This program path. Select Browse to locate your instance of SQL Server. The program is called sqlservr.exe. It's usually located at:
C:\Program Files\Microsoft SQL Server\MSSQL<InstanceName>\MSSQL\Binn\sqlservr.exe. Click Open, then Next.


6. Under Action, select Allow the connection. Then click Next.


7. In Profile, select the profiles that apply to your network configuration then select Next.
Warning
Note
Take into account that enabling the rule for the Public profile may expose your network to security risks, and you may need to add other security measures that fit your needs.

8. In Name, type a name for the rule then select Finish.



IV. Configuring Thinfinity Workspace

Connect Thinfinity Workspace to the Configured Database

Alert
Important!
You will have to apply this configuration to each Thinfinity Workspace Primary Broker that you wish to connect to the SQL Database.
To do that, follow the steps:

1. Open the Thinfinity Configuration Manager and navigate to the Database tab. Then, to the right of Database Connections field click the + sign to add an SQL database connection and give it a name then click OK.
2. Back to the Database tab, complete the following fields:

Server Name = SQL Server name\Instance name
Database Name = The name of the SQL DB you just created
User Name = SQL DB User name with admin privileges
Password = Password for the SQL DB admin user
When finished, click Test Connection and you will receive a Connection successful message.


3. Finally, select the System Components that will use either the Local or the SQL DB and click Apply.



You are now ready to share your Thinfinity Workspace configuration among multiple Primary Brokers and improve their performance.

This document provides comprehensive guidance on configuring a shared local database using SQL Server within Thinfinity Workspace. With this configuration, users can expect improved performance, enhanced security and consistent operation of their Thinfinity Workspace environment.

If you have any further inquiries or need additional support, please do not hesitate to reach out to us. Our team is always available to help address any questions or concerns you may have.

    • Related Articles

    • Thinfinity Secondary Brokers - A Technologically Advanced and Secure Alternative for Accessing OT Networks

      Executive Summary Operational Technology (OT) networks are integral to modern industrial operations. Traditional methods of accessing these networks, such as VPNs and jump servers, have become increasingly problematic due to security vulnerabilities ...

    • How to Configure VirtualUI Sessions

      Product: Thinfinity Workspace Versions: 7 and later Introduction Welcome to the VirtualUI Sessions configuration guide for Thinfinity Workspace. This concise guide provides the instructions to ensure the successful configuration of VirtualUI ...

    • Configure Single Sign-On Using RADIUS

      Product: Thinfinity Workspace Version: 7 and above RADIUS (Remote Authentication Dial-In User Service) is a networking protocol used for centralized authentication, authorization, and accounting (AAA) for remote access services. It enables secure ...

    • How to Create Your First RDP Connection Using Thinfinity as a Jump Server

      Introduction Welcome to this comprehensive guide designed to facilitate the setup of your initial RDP connection using Thinfinity® Workspace. Within this guide, we'll provide a detailed walkthrough on configuring Thinfinity Workspace as a jump ...

    • Configure Single Sign-On Using PingID with SAML

      Product: Thinfinity Workspace Version: 7 and above PingID SAML (Security Assertion Markup Language) enables single sign-on (SSO) by acting as an identity provider (IDP), allowing users to authenticate once with PingID and securely access multiple ...