[EMAIL PROTECTED] writes: >Not sure what to tell you - check to see if you have logging enabled on your Logging is not enabled. >
>This is a longshot, but you might have had a corrupted index that >inaccurately reported 75k records when you really were only at 13k, and >optimizing the table did something to correct it? The reason I suggest this >is because 11 megs for 13,000 records sounds right if you have a fairly >complex table, while 11 megs for 75,000 records would say that you have only >a few fields in your table. Not sure which is more accurate, but that's a >guestimate. > It's a fairly simple table, about 20 fields. The text only version of the data, which I imported from, is approx 11MB. When I mysqldump what's left of the database to a --tab file, the size is 2MB, so the 11MB seems to be the right size. For the full table. If I open the .MYD file with a texteditor, I still have approx 60,000 rows of data (consisting of more records, I'm sure, since many records often occupy each row). So I now I'm sure the data is in there still. So how do I get it back? I'm going to try the myisamchk to see if that works. > > >It's a bit too late for this, but you should be keeping daily backups I deserve foul language and abuse for not setting up the daily backups sooner. I was just getting to it today, as a matter of fact. *-P Paul Fabris IT Manager Market Connections Inc. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
