Hi,
I have decided to replace my existing HTPC with a brand new system. My plan was to migrate all the data first - all done successfully - and then to migrate the MpTvDb from the old machine to the new one using the MySQL Workbench tool - again all worked fine.
Except that.....
TVServer now won't work properly because the TV cards are different and it fails to start/stop the database due to an error in getting the card. My assumption at this point is that this is because it's trying to load a card that doesn't exist on the new system.
Obviously I would like to preserve as much of the old database as possible, largely because it contains all the TVWishList data as well as preferred channel groups and so on, and doing this will save a very large amount of time in trying to rebuild several years of data.
Obviously one possible solution - I think! - would be to migrate all the tables except for those containing the card and tuning data. Once this is done I could then just rescan on the new cards.
Would this work OK? If so, can anyone tell me which are the tables I need to leave out of the migration process? The MySQL Workbench make this fairly easy to do once you know the specific tables to handle.
I have decided to replace my existing HTPC with a brand new system. My plan was to migrate all the data first - all done successfully - and then to migrate the MpTvDb from the old machine to the new one using the MySQL Workbench tool - again all worked fine.
Except that.....
TVServer now won't work properly because the TV cards are different and it fails to start/stop the database due to an error in getting the card. My assumption at this point is that this is because it's trying to load a card that doesn't exist on the new system.
Obviously I would like to preserve as much of the old database as possible, largely because it contains all the TVWishList data as well as preferred channel groups and so on, and doing this will save a very large amount of time in trying to rebuild several years of data.
Obviously one possible solution - I think! - would be to migrate all the tables except for those containing the card and tuning data. Once this is done I could then just rescan on the new cards.
Would this work OK? If so, can anyone tell me which are the tables I need to leave out of the migration process? The MySQL Workbench make this fairly easy to do once you know the specific tables to handle.