[TV] Repair TV database from within MP or config (1 Viewer)

[joostzilla]

Not very often but occassionally the TV database gets corrupted.
To fix this you have to go through a lot of not so user friendly steps. (if you can identify the problem)
Wouldnt it be possible to do this fix from within MP or configuration?

 

[azzuro]

@mm1352000 / @gibman
as we rework TvE, is not possible to add this feature ??? at least planned for future enhancement

Gui :
When we are this issues related to DB

• "Unknown error" related to bad closing DB
• Db corrupted

Have an ask if Error unknown is displayed almost 3 times > Popup = "You have Error 3 times succesive, Do you Want try to repair database ? > Yes / No "
For single-seat and multi-seat

Gui setting > Tv :
"Try to repair Db" button

Tvserveur setting -> Manual control :
"Try to repair Db" button

 

[mm1352000]

Moving to the MySQL InnoDB transactional DB engine should mean this problem is taken care of.

 

[azzuro]

i have already moved to innoDb ( if i remember good) and yesterday i have crash of DB

 

[mm1352000]

i have already moved to innoDb ( if i remember good) and yesterday i have crash of DB

I suspect you're not using InnoDB if you have a crash.

 

[azzuro]

let me verify this, i revert to you later ( here)

 

[radical]

Moving to the MySQL InnoDB transactional DB engine should mean this problem is taken care of.

Full agree. Using MySQL 5.6 with InnoDB since nearly 2 months without crash. Previously I had almost every week a crash with MySQL 5.1.

In my opinon updating MySQL database should have priority over a repair function.

 

[azzuro]

i have arelady updated to 5.6, but i'm not sure to have updated my DB to innoDB

 

[Vasilich]

Wouldnt it be possible to do this fix from within MP or configuration?

MP itself has no connection to DB - only TVService does. And this is not an option for background windows service to periodically repair possible DB corruptions. Moreover - there are different repair approaches for 2 supported DB engined (MySQL and MS SQL).
As others said, you have 2 possibilities:
1. Switch to MySQL5.6+InnoDB
2. start a batch script that repairs DB.
First solution is preferable because DB just won't get crashed. But if you plan to move to InnoDB later - i can give you my script that i use in HTPC autostart, though it can be used in manual mode(it stops/kills TVService, repairs DB and starts TVService again).

 

[azzuro]

So, you are right, is MyISAM DB