I keep seeing posts on the Spacial forums from users having headaches with SAM Broadcaster and MySQL.
This is nothing new I’ve written about the SQL structure in SAM Broadcaster being badly written before.
Users are being told they cannot use MySQL 5.6 with SAM Broadcaster and have to use 5.5 instead.
That just screams Lazy SQL programming to me.
The SAM Broadcaster SQL tables haven’t really changed for over 6 years and the database is prone to crashing.
Where as RadioDJ will work with MySQL 5.6 (Although we recommend MariaDB) and the tables don’t appear to crash like the SAM Broadcaster ones do.
If you are having SQL headaches with SAM do yourself a favour uninstall SAM and Install RadioDJ free radio automation software instead & you’ll be better off in the long run.
The database tables in RadioDJ rarely seem to crash or need a repair.
We know of users who have had RadioDJ running for over 17 months without so much as a hiccup.
People need to wise up to the fact Spacial Audio just take people’s money for their software without actually doing any work to upgrade their SQL tables or the software itself.
My advice as always is Don’t pay Spacial Audio $$$ for software that isn’t up to the job
You won’t get any support when things go badly wrong with your database.
Last updated on: May 31st, 2017
at 13:29 PM Europe/London