Saw this post on a forum on a post about RadioDJ free radio automation software.
So Why does RadioDJ rely on a MYSQL database?
RadioDJ requires MySQL to run some backend functions such as Rotations/Playlists/Events and even listener requests.
The fact RadioDJ relies on an SQL database for some of it’s functions is actually one of it’s PLUS points.
Having an SQL database makes programming on your (PHP) website really straight forward, You can show what’s currently playing or recently played or as mentioned take listener requests.
Other radio automation programs that run with a flat file system don’t appear to have any form of web integration.
With RadioDJ You can take a database backup on one machine and then easily restore it on another machine using the database backup tool. So you have all the same songs/rotation/events on different machines.
As far as we know you cannot do that with other well known paid for radio automation software.
WE never hear anyone question why another well known automation program comes with 4 different database options…
MySQL isn’t that scary once you get used to the basics and the database with RadioDJ has been kept simple, and easy to configure.
We use MariaDB to run our copy of RadioDJ with and never have an issue.
The database structure in RadioDJ is that stable/reliable users aren’t having to constantly rebuild the database every week/month
We haven’t had to rebuild our database since June 2014 & we take a daily backup of it using the backup tool.
Can we please get past this MYTH that RadioDJ needing an MySQL database being a bad thing?
If YOU took the time to get used to what RadioDJ can do for you and your radio station then you would realise why it has a database structure.
Another plus point for having a MySQL database with RadioDJ?
You can organise your music collection as you want it… Not how software like iTunes wants to reorganise it for you.
Last updated on: July 19th, 2017
at 14:28 PM Europe/London