SAM Broadcaster Pro comes with four different options of database to install.
Firebird – MySQL – PostgreSQL – MSSQL
Of the four different database options that come with SAM Broadcaster, Firebird appears to be the most unstable database of the options you’re given.
We quite often see users complaining that the Firebird database in SAM Broadcaster has crashed on them and that they’ve lost all their data.
This was another recent search made on Google as its shown up in Google analytics.
Firebird only allows you to load a maximum of 50,000 songs so it’s not great if you have a huge music collection.
Whereas there are users of RadioDJ with 300,000 tracks in their databases.
The MySQL database in SAM Broadcaster doesn’t fare any better as that’s also prone to crashing or becoming corrupted especially if SAM Broadcaster Pro crashes without warning.
The SQL database in RadioDJ is far more stable and lets you load as many songs as you need.
You can find a tutorial on how to setup a MySQL Server for use with RadioDJ Here
The database in RadioDJ seems to be a lot more robust and stable. It’s over 5 years since we last rebuilt the MariaDB SQL database from scratch.
The Firebird database that comes with SAM Broadcaster just isn’t fit for purpose. It’s just another reason to stop buying software from Spacial Audio.
A: It shouldn’t do as they run as separate services on separate ports.
A MySQL server it shouldn’t crash like the Firebird database does. We’ve had 1 crash in 5 years and that was after a powercut & was easily remedied using HeidiSQL to fix it.
Update Jan 2019
We’ve recently seen someone having stability issues using Firebird with SAM Broadcaster. Nothing ever changes its the same old broken software being released year after year.
Last updated on: 25th September 2019
at 07:31 AM Europe/London