In general when using a relational database for client data storage, is it a good idea to archive data older than a certain date (like say 2 years) or just let good indexes take care of data growth? For example, we would move all data out of certain tables that grow very large (approx. 20K - 40K records, growing by 10K / yr.) to tables that aren't used often. This theoretically would speed up queries on those often used tables. The downside of course is writing new queries that use the "archived" tables to get old data when needed. So my question is: What is the standard practice for this issue? Archive or not? James Davis Software Engineer Kaleida Systems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Enterprise web applications, build robust, secure scalable apps today - Try it now ColdFusion Today ColdFusion 8 beta - Build next generation apps Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:289141 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
