I've been reading High Performance MySQL today and got some great
tips
from that which will help a lot.
Yes it is a good book. I hope you have the 2nd edition.
I do, I should have read this years ago (well.. the 1st edition then
at least). So many caveats to using indexes.
So why not have 2 tables: "Cases_Active" for the cases currently
open, and "Cases_Closed".
Reporting across open and closed, but as you state I could be using
UNION for this. Reporting is not expected to be fast any way.
You can use a Memory table but they don't work with Merge tables. I
would only consider this if the table gets updates every second or
two and that flushes the cache. I'm not sure how much money you're
willing to throw at this project, but I know of some additional
hardware that can squeeze out more speed.
Well.. I could just throw some more RAM at it. But ideally, I would
have a sound setup first before considering mindlessly adding
resources (however tempting it is).
Thanks for your tips. I'll be looking further into splitting the tables.
Morten
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
