Removing the clobs will also greatly reduce the size of the tables (assuming the clobs are not stored inline). This was a really interesting article showing the effects of clobs on table size, and it comes from a reliable source.
http://tkyte.blogspot.com/2007/02/i-learn-something-new-every-day.html Axton Grams On Nov 8, 2007 10:29 AM, Axton <[EMAIL PROTECTED]> wrote: > Have a couple of ideas that I would like to request comments on > regarding the CMDB and Oracle Partitioning. I see these actions as > something that would greatly improve the performance of the CMDB for > things like RE jobs. I am working against CMDB 2.0.1 patch 3. > > 1. Has anyone removed the clobs from all the classes? The only ones I > see follow: > BMC.CORE -> Base Element > Notes > History > BMC.AM -> Inventory Storage > Activity Log > Maintenance Log > > This will allow the possibility of parallel execution during queries > to the tables. > > 2. Has anyone partitioned the CMDB data based on the DatasetId? This > follows the model in place within the CMDB to partition the data sets > and would allow operations against the data sets to run run much > faster in the case there is a table or index range scan (given that > the indexes are partitioned as well). > > Thanks, > Axton Grams > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
