List:General Discussion« Previous MessageNext Message »
From:SGreen Date:October 12 2004 2:06pm
Subject:Re: splitting a large table - does it improve performance?
View as plain text  
Absolutely!

Smaller tables = smaller indexes.  Smaller indexes also mean faster 
look-ups and faster record inserts.  You could eventually drop indexes on 
the older tables, saving disk space (by comparison, you can't index only 
part of a table).  Once a table becomes so old that no updates will be 
performed on it, you can even compress it saving additional disk space.

Tables that are rarely used can be moved into near-line storage (a Network 
share or a SAN device) so that you save the faster local disk for the 
other 95% of your queries.

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine

"Ronnie Sengupta" <ronnie_sengupta@stripped> wrote on 10/12/2004 
02:11:44 AM:

> "Does splitting a large table (20 Million rows) growing at 5 million or 
more
> a month into smaller tables improve performance given that the table can 
be
> split in a logical way such that 95% queries don't need to look at data
> spanning across the split tables"
> 
<snip> 
> 

Thread
splitting a large table - does it improve performance?Ronnie Sengupta12 Oct
Re: splitting a large table - does it improve performance?SGreen12 Oct
  • Re: splitting a large table - does it improve performance?mos12 Oct
    • Re: splitting a large table - does it improve performance?Eric Bergen12 Oct