Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Web Help Desk (WHD) > Web Help Desk (WHD) Documentation > Web Help Desk 12.5.2 Installation Guide > Plan for a production deployment > Prepare the Web Help Desk database

Prepare the Web Help Desk database

Updated: July 6, 2017

SolarWinds Web Help Desk supports the following databases:

  • Embedded PostgreSQL 
  • MySQL™
  • Microsoft® SQL Server Standard or Enterprise Edition

If your Web Help Desk deployment requires database management features such as failover clusters, do not use the embedded PostgreSQL database included with Web Help Desk. Failover clusters are not available with the embedded PostgreSQL database.

If you choose embedded PostgreSQL as your primary database, Web Help Desk installs the database on the Web Help Desk server during the installation. No additional configuration is required.

If you choose non-embedded, non-default Microsoft SQL Server or MySQL as your primary database, install the database engine and management tools on a separate server prior to installing Web Help Desk. See the Microsoft Technet or MySQL website for installation instructions.

Install SQL Server or 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. You can also configure Web Help Desk to use a new SQL Server database instance on an existing server running SQL Server.

After you install the MySQL software, prepare the MySQL time zone tables.

After you install the SQL Server software, enable TCP/IP on the SQL server and create and configure your SQL Server database.

Prepare the MySQL time zone tables

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:

  • time_zone
  • time_zone_name
  • time_zone_transition
  • time_zone_transition_type

These tables are created when you install MySQL in your deployment, but are not populated by default with data. Web Help Desk requires this data because 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 on SQL Server

Configure the following settings in the SQL Server Configuration Manager.

TCP/IP ProtocolEnabled in SQL Server Network Configuration > Protocols for SQL 20xx
IP Address (if installed on the Web Help Desk server)

Server IP address (if installed on a separate server)

TCP Port1433
TCP Dynamic PortsBlank

Create and configure your SQL Server database

Configure the following settings in the SQL Server Management Studio for SQL Server to create and configure SQL Server to the Web Help Desk database instance.

SQL Server and Windows Authentication ModeEnabled
Login Namewhd
SQL Server Authentication: PasswordEnabled and configured
SQL Server Authentication: Enforce password policyDisabled
SQL Server Authentication: Enforce password expirationDisabled
SQL Server Authentication: User must change password at next loginDisabled
Database namewhd
Database ownerwhd

Last modified