Any active log file -- even in SQL, runs the chance of having problems on disk I/O, or due to system problems.
You need to run the ISAMCHK program on the database regularly, and look for problems. It's a good idea to run it as a cron job, have it output to your email every morning so you can review it.
If you look (well, if you maintain a lot of sites) on links 1.1x the "hittrack" table was the one that was always getting corrupted, since it was almost always open, and on AdvertPro the same thing happens to the log file there.
It's just a problem with active files remaining open. The indexes get corrupted. I'm not sure the data does, as long as you repair the indexes on a regular basis.
PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
You need to run the ISAMCHK program on the database regularly, and look for problems. It's a good idea to run it as a cron job, have it output to your email every morning so you can review it.
If you look (well, if you maintain a lot of sites) on links 1.1x the "hittrack" table was the one that was always getting corrupted, since it was almost always open, and on AdvertPro the same thing happens to the log file there.
It's just a problem with active files remaining open. The indexes get corrupted. I'm not sure the data does, as long as you repair the indexes on a regular basis.
PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
