In these days of striping and disk caching I'm not sure that we get benefits from attempting to control where data is written.
My own view on this is that to get the best performance a monthly algorithm will provide both best performance and practicality if; Current month data is kept on fast SSD Non current is kept on physical disk Archive is kept on cheap physical disk I get archiving for free, by this I mean that I can simply move the part file when the data contained has reached the purge dates (due caveats about table interactions) I do have to do more work as a DBA to manage this setup (create the part files and move data) but I think this is a price worth paying. I also believe with monthly distribution you can have a faster algorithm (which is probably as important as the speed of the write) by having a CASE that tests the internal date against the ID[whatever length] Regards, John. -- -- IMPORTANT: T24/Globus posts are no longer accepted on this forum. To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
