Hi All,
Is anyone in particular leveraging oracle partitioning to help with
performance and scalability?
I am investigating options other than archiving to a seperate form since that
method breaks reports that require access across a large span of data, unless
you build unions between tables in a seperate environment, that would require
considerable extra work in customizing the Analytics universe within ITSM 7.5,
and affect the upgrade path repeatedly.
I'd also like to respect the OOB functionality of being able to link requests
together. If we archive requests to a different form, we will lose the ability
(without customization) to navigate to a request from the relationships tab of
either the CI, other Incident, Problem record if it is archived to a seperate
form.
The only think I can think of is using table partitioning, but I'd like to see
if others have got the expected results using this method, or if there are any
other methods you may be using.
Thanks
Randeep
_________________________________________________________________
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
