If you are frequently deleting many records, then that can cause
fragmentation. But if you are deleting that many records, you usually
are deleting "old" records. To work around this overhead, I usually
use MERGE tables. On a periodic basis you create a new table, add it
to the MERGE list while also removing the oldest table from the MERGE
list. You still have all the data, but you've removed it from normal
use with virtually no overhead.
Brent Baisley
On Nov 17, 2008, at 9:53 PM, Micah Stevens wrote:
I don't think this is indicative of a design issue. Some tables need
data removed more often than others, however Moon's Father brings up
an excellent point. If you CAN resolve this with a change in design,
that would be the best solution of course.
-Micah
On 11/17/2008 06:50 PM, Moon's Father wrote:
Maybe your tables were not properly designed.
On Tue, Nov 18, 2008 at 10:35 AM, sangprabv <[EMAIL PROTECTED]>
wrote:
Thanks for the reply, does this overhead reduce performance? And is
there any tips to avoid this overhead? TIA.
WM
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
