Considering Your Web Help Desk Database Options

mwwilk over 10 years ago 2 minute read time

When you're setting up a new Web Help Desk v12.0.X installation or upgrade, how carefully should you consider your database options? It depends what's most important to you. Are you looking for the easiest installation? Are you upgrading or performing a brand new installation? Are you already running a supported external database?

About Web Help Desk-supported Databases

WHD v12.0.X uses an embedded PostgreSQL database as its standard database and no longer supports FrontBase, OpenBase, or Oracle databases. If you are upgrading to WHD v12.0.X and have been using an embedded FrontBase database, the WHD installation wizard walks you through upgrading from the FrontBase database to an embedded PostgreSQL database.

WHD also supports Microsoft SQL Server versions 2008 and 2012 and MySQL version 5.5 as external databases. You can use an external PostgreSQL 9.2 or 9.3 database with WHD v12.0.X as well.

Recommendations

For most installations, SolarWinds recommends using the standard embedded PostgreSQL database. This Web Help Desk Getting Started Wizard walks you through the complete installation of this database when you do a fresh install. Or, if you're doing an upgrade from FrontBase, the Getting Started Wizard automatically performs the database upgrade for you, and you don't have to do anything!

If you already have an external PostgreSQL 9.2 or 9.3, SQL Server 2008 or 2012, or MySQL 5.5 database up and running, you may want to use that database as your Web Help Desk database. If you using an external database, SolarWinds recommends installing WHD and the WHD database on separate servers, with the WHD database hosted on a Microsoft SQL Server or MySQL server.

If you are running an unsupported database, such as Oracle or FrontBase, you will need to migrate to one of the supported databases. Not an impossible thing to do, but there is some work involved. One of the things you'll need to do is convert the datatypes in your existing database to the datatypes used in the new database. You can perform these conversions using third-party tools such as PGAdmin3 or PostgreSQL Data Wizard. For details on migrating from an external or unsupported database to PostgreSQL, see Converting from other Databases to PostgreSQL on the PostgreSQL website. This article covers database migration from many databases, including:

FileMaker Pro
IBM DB2
Microsoft Access
Microsoft SQL Server (SQL Server)
MySQL
Oracle

For more information on making the most of your Web Help Desk installation, check out these free Web Help Desk use case and training videos.

Top Comments

jvbarnes over 10 years ago +1

Just curious if you can explain why Postgre is recommended over MS SQL in most instances.Thank you! I'm getting ready to install a fresh installation on a dedicated server. It appears Postgre will be simpler…

jkump over 8 years ago

Interest post and comments.
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
jr3151006 over 9 years ago

There is a way to install (from scratch) using MS-SQL or should I install using PostGree and then convert it?
I´m curious since I saw MS-SQL option but I´m unable to found a script for example to create a new db and its structure.
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
scottmccoy over 10 years ago

I'm interested in that very same question. My concern would be performance, running it all on one server using the embedded PostgreSQL db. That kind of goes hand-in-hand with my question of going the virtual appliance route. I like the simplicity but it's all running on the one VM.
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
jvbarnes over 10 years ago

Just curious if you can explain why Postgre is recommended over MS SQL in most instances.Thank you!
I'm getting ready to install a fresh installation on a dedicated server. It appears Postgre will be simpler to get up and running quickly, but will be be sacrificing any functionality down the road?
- Cancel
- Vote Up +1 Vote Down
- More
- Cancel