Re: Minimum number of rows for using partitioning
*****(TIMESTAMP > xxx) AND (TIMESTAMP < xxx) -- what are the typical values of xxx? Perhaps units of days? Or hours? Do you really need resolution of 5 seconds? What do you do with the SELECT? Look for min/max/average/total? I'm leading toward summarizing the information over some bigger unit, say 5 minutes. This would require 1/60th the number of rows. The data would have other things -- like min, max, count, sum. Average = sum/count.
[Ramesh] My application is an trouble shooting application which should have data with lowest granularity(5 seconds). I'll populate graphs based on time interval given by user input. Mostly it would be 1 hr. Some times user may view day wise data. The AVG/MIN/SUM functions will be used only in reports which will view rarely. But in future, I have plan to store one hr min/max/avg data which will be used for reporting.
*****You also said there were performance problems "due to indexing".
[Ramesh] No. Sorry. There is some miss-communication. I didn't face any performance issue. My application really doing well due to proper indexing. Even though, it is doing well, I would like to use new partition technology to boost my application to get extra benefit.
Thanks,
Ramesh
Edited 1 time(s). Last edit at 12/14/2009 12:58AM by Ramesh Kumar.
Subject
Views
Written By
Posted
5195
December 10, 2009 10:57PM
2352
December 12, 2009 10:58PM
2650
December 13, 2009 09:57PM
2308
December 14, 2009 12:17AM
Re: Minimum number of rows for using partitioning
2652
December 14, 2009 12:57AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.