Missing the point?
April 8, 2008 - 8am Central time zone
Reviewer: A reader from FL
"as long as you met the goal you wanted to meet with regards to partitioning - which it sounds like
you did - easier administration."
Why do you assume the user's goal is easier administration? I don't see that at all. I think the
user is looking for better performance since he also talks about using bitmaps indexes which has
nothing to do with easier admin.
I also see the user's concern regarding unbalanced list partitions. Yes, to find the data for an
entity is a simple partition scan but seems to me it will take longer to scan a partition with
several gigs than a partition with a few megs. I think this is the whole point, not easier admin.
Followup April 9, 2008 - 2pm Central time zone:
because EVERYTHING mentioned in the question was about "ease of adminstration"
They stated they partitioned to truncate in the event of a reload. That is by definition ease of administration.
everything they said regarding partitioning was about ease of administration.
there was this red herring of a bitmap index - something that would not have done a thing for performance (rather the opposite in this case)
Didn't miss the point
April 8, 2008 - 8am Central time zone
Reviewer: Mike from Cleveland, OH USA
Given that the questioner said:
In the event we receive a new set of data, I can simply truncate the existing partition and reload
the new data.
(and other related points)
and said nothing about using partitioning for a performance goal, I would also have concluded that
'ease of administration' in managing the entity sets of data was the primary motivation here.
Performance + ease of administration.
April 8, 2008 - 10am Central time zone
Reviewer: Kashif from Reston, VA
To the reviewers,
Thanks for your input. My prime concern is performance, administrative ease is secondary, though I
don't see why addressing what my objective is necessary here, the answer would still have been the
same?
To Mike from Cleveland,
Truncating partitions is also a performance gain, consider the alternative of having to delete from
an unpartitioned table using an entity id. With the partition truncate, I can get rid of the
entity's data easily, instead of potentially full-scanning the table to retrieve the rows to be
deleted.
Kashif
Followup April 9, 2008 - 2pm Central time zone:
...Truncating partitions is also a performance gain, consider the alternative of ...
not day to day - second to second. As a person that works with Oracle a lot - the only thing I could derive from your original problem statement was "ease of administration"
Hmm...
April 9, 2008 - 4pm Central time zone
Reviewer: Kashif from Reston, VA
I'm not sure what you mean by "not day to day - second to second". Truncating a partition would
typically be quicker than deleting, no?
Kashif
Followup April 10, 2008 - 10am Central time zone:
meaning, this is an administrative task you would perform once in a blue moon - no frequently. One would not think of it as a "day to day, second to second performance improvement"
rather, it makes an administrative task easier and more efficient to perform, that is all.
Hopefully, this is something that hardly ever happens (else I'd be looking hard and long at my process and figuring out why it is so broken)
|