I don't know why BMC would EVER say that you shouldn't have more than 1000 CI's for one change.
What happens in any large company when they issue a Microsoft patch for their desktops? I know for our customers there could easily be many thousands of things connected. That said, quality time with the SQL logs is the way to go. Run the log analyzer of your choice and get on the indexes. We've see query times for some things go from 2M 30S (for a query repeated for every CI update) down to under 1 MS. That changed our processing time from 3 seconds per CI to 15 CI's per second. I am a big BMC fan, but I think they need to do MUCH more testing with large volumes of data. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jamie Sent: Friday, August 22, 2014 12:25 PM To: [email protected] Subject: Re: 8.1.01 Change Approval Performance Issues Thanks for the feedback LJ. I still need to go through the SQL logs to see if indexing can improve things, which is on my list to do but wanted to also reach out in parallel to the list in case others have already fought this. I've attached the form of CHG:Change-ImpactedAreasCIAssociation_outer_ApproverLookup to this message to show how horrific this is set up :). _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4745 / Virus Database: 4007/8066 - Release Date: 08/19/14 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
