| criteria for partitioning [message #335602] |
Tue, 22 July 2008 23:07  |
eaganfox
Messages: 6
Registered: July 2008
Location: Minnesota
|
Junior Member |
|
|
Are there any rules of thumb (numbers) to determine when a table in an OLTP environment should be partitioned? This is as part of strategic planning for that table as there are no performance problems at present. Can we say for instance that partitioning should occur when a threhsold is reached with X number of records, or X bytes of data, or X number of inserts/deletes?
[Updated on: Tue, 22 July 2008 23:10] Report message to a moderator |
|
|
|
|
|
|
|
|
|
| Re: criteria for partitioning [message #337744 is a reply to message #336291] |
Fri, 01 August 2008 00:30  |
sunil_v_mishra
Messages: 506
Registered: March 2005
|
Senior Member |
|
|
eaganfox As you are at stage of planning...
So Try to find out.... is your table is going to do select only or update only or insert only?
If you are going to insert only than partition will not be benefited, but fact is in real life 95% time we need access to the record we stored inserted.
Partition is helpful when you have to do search (select) and also when you have to update... coz for update you have to search record than you have to update...
If Data will frequently change for any particular table in OLTP and table size will grow very fast in future than better to have partition table.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
