Partitioning huge table [message #656512] |
Sun, 09 October 2016 13:14 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](http://www.gravatar.com/avatar/9e9f439c25ebcda2d887d34bd39eec3b?s=64&d=mm&r=g) |
arifmd1705
Messages: 37 Registered: May 2016 Location: uae
|
Member |
|
|
Hi experts,
I have a huge table containing data for around 10 years , like it is a transaction table, and data keeps on getting added.When i run the query or select it , if full table scan is performed , queries are becoming slow.Is there a method to partition the table and use only records of current year or data which is recent for transaction and querying while storing the data on some sort of partition like rarely used data, and in case if i require i can fetch it from there.
|
|
|
|
Re: Partitioning huge table [message #656514 is a reply to message #656512] |
Sun, 09 October 2016 13:28 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
John Watson
Messages: 8944 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
This sounds like an ordinary tuning question. You need to to provide the ordinary information! The statement, the execution plan, the DDL of the objects, and so on.
Would partitioning help? I don't know. I do know that it is expensive. In my experience, partitioning is very much the last resort for SQL tuning. Specially in your old 10.something release. It is much better in 12.
|
|
|
|
|
|
|
|
|