Re: Using DISABLE KEYS on production tables

[Dave Scofield]

I anticipate about 4 million rows in total - but that will be broken up over several hundred customers, each deciding to migrate their data on their own timing. Within each customer it'll be a year's worth of rows at a time, which is a number that varies too much to even guesstimate, and within that it'll be a month at a time in a single statement, separated by sleeps. I think it'll be ok.

The current application does very little reading, and even if someone's SELECT gets blocked and has to take the long route, it'll be over the *much* smaller new (and normalized) database.

Thanks again for your help and insight!