Both Jusung and Sybrand are correct. You have to think about what
partitioning does. One objective is that you can control different parts of
a table - a partition - on different IO devices. Maybe you have one
partition that is used heavily and the others are not. Might be a good idea
to put the heavily used one on the device with the fastest IO and the others
on slower IO (eg cD-rom) devices.
It depends. Think about what it does, experiement, benchmark.
Jim
"Jusung Yang" <JusungYang_at_yahoo.com> wrote in message
news:130ba93a.0212151449.72d33e4e_at_posting.google.com...
> Well, there is no such fixed target of number of records beyond which
> partitioning would make sense. Safe to say if you have 100 records in
> a table, partitioing would be a overkill. On the other hand, if you
> have millions of records in the table, partitioing would make a lot of
> sense. You will have to decide for yourself if partitioning is
> appropriate for your environment - based on how big the table is, how
> the data is populated and what kind of queries will bw run aginst the
> table.
>
>
> - Jusung Yang
>
>
> "Danny Stoll " <d.stolle_at_info.inf> wrote in message
news:<rG4L9.84875$e%3.3249678_at_Flipper>...
> > i did all this, the answer i want on my question 'WHEN IT IS PREFERABLE'
is
> > not discussed. Like e.g.: do you start partitioning when your table
exceeds
> > the 1 million record or is it preferable to partition when you expect
more
> > then 100.000 records????
> >
> > the discussionboard didn't give me the answer, sorry!
> >
> > Danny
Received on Sun Dec 15 2002 - 17:21:53 CST
