Corrupt EPG database. (1 Viewer)

[Anumator]

Hi, I'm having trouble with XMLTVGUI I've tried importing the XML files in TV server but it says it's already importing, but it doesn't do anything !. I've looked around for answers on this site and found that others have had the same problem, and the answer is to use this command, CD C:\Program Files\MySQL\MySQL Server 5.1\bin
mysqlcheck mptvdb --auto-repair -e -u root -p
My problem is I can't get this command to work , I open the MySQL monitor window enter the password, type in the command as written above, but I get an error message - Unknown command \M \M \b , I'm obviously doing something wrong can anybody help ?

 

[arion_p]

you run that from the command line, not mysql monitor window.
Note that these are 2 commands:

CD C:\Program Files\MySQL\MySQL Server 5.1\bin
mysqlcheck mptvdb --auto-repair -e -u root -p

 

[Anumator]

Thanks - that worked ! I Didn't realise it was two commands either. EPG now running smoothly for five minutes ! I wonder, is there another more reliable method of importing EPG's?

 

[arion_p]

This has nothing to do with the way EPG is imported. EPG is stored in the database. If the database is corrupt, you cannot import EPG no matter what method you use.
The problem is that by default MySQL uses MyISAM engine which is not transactional. If a power failure or other unexpected system shutdown occurs, data may not have been flushed from memory to disk and the database gets corrupt. There is another engine, InnoDB, which is transactional and does not suffer from this issue (unless the filesystem itself gets corrupt), but it comes at a cost: speed. InnoDB is considerably slower than MyISAM. If you expect your system to be randomly powered off without proper shutdown you may want to convert your database to InnoDB.

Another option is to use MSSQL (Express) which is always transactional and also does not suffer from this issue. It is also slower than MyISAM but to my experience faster than InnoDB (no have not performed any benchmarks so I may be wrong). But MSSQL by default uses ANSI encoding for strings which means only characters from a single ANSI charset are supported. If you need characters from non-latin character sets (such as Greek, Cyrillic, etc) you need either MySQL or you need to change the database fields from varchar to nvarchar. Unless you know what you are doing I suggest you avoid it.