| Efficient Data Management. [message #307857] |
Thu, 20 March 2008 03:21  |
Oraclist
Messages: 33
Registered: January 2008
Location: Dhaka, Bangladesh
|
Member |
|
|
In my database table there are millions of rows. But the latest 3 months data is frequently needed. And queries on this rows (data) take much time that we want. How can I manage this scenario so that performance will improve.
I consider one case is to partition the table and keep the latest 3 months data in separate partition and keep them in keep buffer pool.
Or I can create a materialize view
Any more idea?
One point: Can I manage my data so that a particular column can be kept in keep pool only rather the whole table column.
[Updated on: Thu, 20 March 2008 03:22] Report message to a moderator |
|
|
|
|
|
| Re: Efficient Data Management. [message #307940 is a reply to message #307858] |
Thu, 20 March 2008 07:43  |
rleishman
Messages: 3728
Registered: October 2005
Location: Melbourne, Australia
|
Senior Member |
|
|
You are mixing two terms: Shared Pool and Buffer Cache.
The Shared Pool contains SQL, the Buffer Cache contains data.
Frequently used data - such as indexes - will be in the buffer cache - you don't need to do anything. Data that is infrequently used (eg. blocks of indexes relating to old data) will get aged out of the buffer cache.
Ross Leishman
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
