Re: .ini settings for ADD KEY to 30Gb table on 96Gb machine?

[Peter Griffioen]

Yep, Exactly, almost 800gb for this table! Most queries would only hit 1 table (year). I've already determined that with the PointId, ModisTileLoadID primary index that this is surprisingly quick to respond. Where I need to get data across many tables, my code may make a MERGE table on the fly.

In the end I need the software to output composite satellite images of say 10,0000 x 10,0000 pixels, 6 bands in an hour or three of crunching. Overnight wouldn't be a disaster but would restrict experimentation. Most importanly I need flexibilty as often we want images to match old field campaigns such as Spring 2006 vegetation condition surveys or Pre and Post 2008/9 fires. None of it is rocket-science but gee it can make the computer grind away for a while!

In the end, it is actually amazing that anything like this can be done at all, with what really are just souped up desktop PCs and Free(!) software. While this may not be the best way to do this, I'm certain I'll get this to work in the next few days. In short, MYSQL leaves me in awe because I've made a few DBs with it now and it is pretty rock solid and extremely powerful. And you have been a great help too Rick. I see your postings all over the place and they are very helpful. Thanks.