<p><tt><font size="2">> <br />> I have a table with 40 million rows and haven't had any performance <br />>
issuesyet.<br />> <br />> Are there any rules of thumb as to when a table starts getting too big?<br />> <br
/>>For example, maybe if the index size is 6x the amount of ram, if the<br />> table is 10% of total disk space,
etc?<br/>> <br />> <br />> -- <br />> </font></tt><br /><br /><tt><font size="2">My rule here is that a
tableis too big when performance starts degrading beyond an acceptable level. </font></tt><br /><br /><tt><font
size="2">Ifthe database and server are delivering consistent and acceptable performance levels despite an index being
6xRAM or a table consuming 10% of disk, then I tend to leave it be until an issue is raised.</font></tt><br /><br
/><tt><fontsize="2">Cheers<br /></font></tt><br /><tt><font size="2">Martin</font></tt><font
face="sans-serif">=============================================Romax Technology Limited Rutherford House Nottingham
Science& Technology Park Nottingham, NG7 2PZ England Telephone numbers: +44 (0)115 951 88 00 (main) For other
officelocations see: http://www.romaxtech.com/Contact ================================= =============== E-mail:
info@romaxtech.comWebsite: www.romaxtech.com ================================= ================ Confidentiality
StatementThis transmission is for the addressee only and contains information that is confidential and privileged.
Unlessyou are the named addressee, or authorised to receive it on behalf of the addressee you may not copy or use it,
ordisclose it to anyone else. If you have received this transmission in error please delete from your system and
contactthe sender. Thank you for your cooperation. =================================================</font>