Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Web Help Desk (WHD) > WHD - Knowledgebase Articles > Migrating external or unsupported WHD databases to PostgreSQL

Migrating external or unsupported WHD databases to PostgreSQL

Table of contents
No headers

Web Help Desk 12.0 does not support an external Oracle® or embedded FrontBase database. If you upgrade Web Help Desk to 12.0 or later, you must update your database to a PostgreSQL, MySQL, or Microsoft® SQL Server database.

To migrate an Oracle or FrontBase database to PostgreSQL, use a third-party migration tool (such as PGAdmin) or PostgreSQL Data Wizard. To migrate to a PostgreSQL database, see Converting from other Databases to PostgreSQL on the PostgreSQL website (© 2017 The PostgreSQL Development Group, available at https://www.postgresql.org, obtained on August 18, 2017).

This resource provides migration instructions for several database types, including:

  • FileMaker Pro
  • IBM DB2
  • Microsoft Access
  • Microsoft SQL Server
  • MySQL
  • Oracle

Disclaimer: Please note: Any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Last modified

Tags

Classifications

Public