| alternate for Table Partitioning [message #422569] |
Thu, 17 September 2009 07:58  |
mr.rajeshyadav
Messages: 48
Registered: November 2007
|
Member |
|
|
Hi,
I am having a table which will have car repair data with 245 columns which will be having some millions of records and will be updated regularly and there is one column model_year and another column repair_date, as of now this table is being partitioned by model year(2006,2007,2008 so on) and sub-partitioned by claim_date date that is every 2 months data will be put into one partition.
for now if the user selects any one model year and certain range of claim dates now as per the new requirement i need to query the table on another column in which the case i should not put the condition either on model_year or claim_date because of which it is going for table scan which is taking hell lot of time so now in this case if i want to query in both the ways that is either by selecting model_year and claim_date or by selecting another column how do i organize my table????
Thanks In advance,
Raj.
|
|
|
|
|
|
|
|
| Re: alternate for Table Partitioning [message #422667 is a reply to message #422631] |
Fri, 18 September 2009 03:53  |
JRowbottom
Messages: 5933
Registered: June 2006
Location: Sunny North Yorkshire, ho...
|
Senior Member |
|
|
Is that 24 indexes on one column each, or what?
If you want any accurate answers, you're going to have to provide some actua useful technical information, such as what the query is, what the indexed columns are, what the explain plan is for the poorly performing query, and so on.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
