WHD supports the following databases:
- Embedded PostgreSQL
- Microsoft SQL Server Standard or Enterprise Edition with server collation set to case insensitive
If your WHD deployment requires database management features such as failover clusters, do not use the embedded PostgreSQL database included with WHD. Failover clusters are not available with the embedded PostgreSQL database.
If you choose embedded PostgreSQL as your primary database, WHD installs the database on the WHD server during the installation.
If you choose non-embedded, non-default MySQL as your primary database, install the database engine and management tools on a separate server prior to installing WHD. See the MySQL website for the installation instructions.
Install MySQL on a dedicated drive with at least 20 GB of space to accommodate the database engine, management tools, help desk tickets, and ticket file attachments. After you install the MySQL software, prepare the MySQL time zone tables.
If you choose non-embedded, non-default SQL Server as your primary database, install the database engine and management tools on a separate server prior to installing WHD. See the Microsoft Docs website for the installation instructions.
Install SQL Server on a dedicated drive with at least 20 GB of space to accommodate the database engine, management tools, help desk tickets, and ticket file attachments. You can also configure WHD to use a new SQL Server database instance on an existing server running SQL Server.
After you install SQL Server on your database server, enable TCP/IP in SQL Server and then create and configure your SQL Server database.
If you choose non-embedded, non-default MySQL as your primary database, install the database and manually populate your time zone system tables.
You can search for tickets using two new qualifiers: Due Date and First Call Resolution. These qualifiers rely on data located in four MySQL system tables:
These tables are created when you install MySQL in your deployment, but are not populated by default with data. WHD requires this data because the Due Date and First Call Resolution qualifier logic is implemented from within the database. If the database is missing time zone data, these qualifiers do not work properly.
When you install your MySQL database, be sure to manually populate these system tables with time zone data. See the MySQL website and follow the instructions for MySQL Server time zone support.
You can check the system tables by executing the following query:
SELECT * FROM mysql.time_zone
If the query does not create new table rows, the tables are not populated with data.
Enable TCP/IP in SQL Server
Configure the following settings in the SQL Server Configuration Manager.
|TCP/IP Protocol||Enabled in SQL Server Network Configuration > Protocols for SQL 20xx|
127.0.0.1 (if installed on the WHD server)
Server IP address (if installed on a separate server)
|TCP Dynamic Ports||Blank|
Create and configure your SQL Server database
In your SQL Server database, verify that the server collation is set to case insensitive. This ensures that WHD initializes the database correctly and prevents database errors when you configure the application.
See the SQL Server documentation on the Microsoft Docs website for details about server collation.
If the server collation is set to case insensitive, go to step 2.
If the server collation is set to case sensitive, create a new database.
- On the server hosting SQL Server, open SQL Server Management Studio.
- In the navigation menu, locate and maximize the targeted SQL Server instance.
- Right-click Databases and select New Database.
- In the New Database window under Select a page, click Options.
Click the Collation drop-down menu and select a case insensitive option.
SolarWinds recommends the following option:
- Click OK.
- Configure the database settings.
- Install WHD on the host server.
Run the Getting Started Wizard.
If you did not create a new database in step 1, create a new database and login credentials using the WHD Getting Started Wizard.
If you created a new database in step 1, add the database name and login credentials in the WHD Getting Started Wizard.
- Open WHD and link the application to the new SQL Server database.
(Optional) Enable SSL encryption.
Configure the following settings in the SQL Server Management Studio for SQL Server to create and configure SQL Server to the WHD database instance.
|SQL Server Authentication||Enabled|
|SQL Server Authentication:
Enforce password expiration
|SQL Server Authentication:
User must change password
at next login