The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

MySQL Master Need (DB Problems from ASP Record Insert Pages)

I think I'm MEMORIZING the MySQL docs, trying to hunt this down problem down. :-)

Problem: Table Corruption that seems to be caused by
insert statements not properly closing the table.

The level of multiuser contention against this table
is fairly low, but does happen, as recordset queries
are being run against this table fairly constantly,
with record inserts happening several hundred times a
day.

I think I've narrowed the problem down: It seems to
be caused by insert statements not properly closing
the database table. At any rate, this is from the
MySQl Manual:

Code:

If you get the following warning from CHECK TABLE or myisamchk:
# clients is using or hasn't closed the table properly
this means that this counter has come out of sync. This doesn't mean that the table is corrupted, but means that you should at least do a check on the table to verify that it's okay.

This is what I get if I do an insert into the table that's getting corrupted, then do a "CHECK TABLE tab_customer;" within a few seconds afterward.