Curious Fellow wrote:
Would there be any issues that could come up from using the library files from the 4.9.8 version to the new version? I would hope that the program would have the settings pretty standard, but this is the biggest hurdle for us as we would want to be up and running as soon as possible once we get the new license. We would rather not set up again when to play the station ID and such again.
The database structure hasn't changed at all since 4.7.4 as far as I know. The changelog for SAM Broadcaster mentions one more change in 2017.6, but I think that was actually only changing the Firebird structure to look more like the one of MySQL.
The database contains: Events (the right half of the event window where you define what the Event should do), Event Times (when to execute which event), Categories, Tracks and the assignment of tracks to categories.
What's not in the database: All the stuff from the config Window, Encoders, PAL Scripts, Statistics Relays, AGC, EQ, DSP Plugins, Input/Output routing, VoiceFX/Mic config and last but not least the arrangement of "SAM Windows" inside the User Interface.
All of that is stored in the two XML config files SAMBC.core.xml and SAMBC.gui.xml
The database will definitely be compatible between 4.9.8 and at least 2018.5 as far as I know.
Again: I strongly suggest creating and restoring backups using built-in tools of MySQL (i.e. either mysqldump commandline tool or using the Workbench Graphical tool that comes with the default MySQL bundle installer for Windows). The built-in one isn't made for this and usually has problems with the default MySQL security settings which prevent the MySQL daemon from writing files to the harddisk itself.