Okay, thanks everyone. I went ahead and added the index. Thad
On Tue, Apr 23, 2013 at 2:53 PM, Jason Miller <[email protected]>wrote: > ** > I am pretty sure I have seen an answer from a BMC person (Doug maybe?) > why the Name field isn't indexed out of the box. If I remember correctly > it was something along the line that they are leaving it up to us to > decided if we need indexing or not. Each organization may have different > indexing needs based on how the CMDB is used and the attributes an > organization chooses to use. > > Jason > > > On Tue, Apr 23, 2013 at 11:32 AM, itsm.support > <[email protected]>wrote: > >> ** >> >> Hi, >> >> There is nothing mention about indexing in CMDB 8.1 to improve >> performance. >> >> We can add index for better performance as per doc provided by BMC. >> >> --------- >> Indexing classes can reduce database query time. >> >> **** >> >> Index attributes that: >> *You expect users to query frequently. >> *Are used by discovery applications to identify CIs. >> *Are used in reconciliation identification rules. **** >> >> ** ** >> >> For more information about identification rules, see the BMC Atrium CMDB >> 8.1 Normalization and Reconciliation Guide.**** >> >> >> If you create an index for a Character attribute, you can save query time >> by setting the QBE Match characteristic of that field to Leading or Equal >> instead of Anywhere.**** >> >> >> Use the Indexes section on the General tab of the CI Class and >> Relationship Class dialog boxes to specify the indexes for a class. You can >> specify indexes on noninherited attributes only. If an attribute is >> inherited form a superclass, you must specify the index for that attribute >> on the superclass. Display-only attributes cannot be indexed, because no >> values are stored for them. >> >> **** >> >> To combine multiple attributes into a composite index, specify as many as >> 16 attributes per composite index. The sum of all attribute lengths in a >> single index must be fewer than or equal to 255 bytes, so Diary attributes >> and Character attributes larger than 255 bytes cannot be indexed**** >> >> ** ** >> >> --**** >> >> Regards,**** >> >> Pawan**** >> >> **** >> >> Vyom Labs Pvt. Ltd.**** >> >> BSM Solutions & Services || ITIL Consulting & Training**** >> >> Email: [hidden >> email]<http://ars-action-request-system.1093659.n2.nabble.com/user/SendEmail.jtp?type=node&node=7583733&i=0> >> || Web Site: www.vyomlabs.com Follow Vyom Labs >> http://twitter.com/#!/vyomlabs || >> http://www.linkedin.com/company/vyom-labs**** >> >> ** ** >> >> *From:* Action Request System discussion list(ARSList) [mailto: >> [email protected]] *On Behalf Of *Thad Esser >> *Sent:* Thursday, April 18, 2013 7:03 AM >> >> *To:* [email protected] >> *Subject:* CMDB 8.1 Index on Name Field**** >> >> ** ** >> >> ** **** >> >> Hello,**** >> >> ** ** >> >> Does anyone have a loaded 8.1 CMDB that can advise me on an indexing >> question? Our current production CMDB is 2.1 and we are moving to 8.1. In >> 2.1, I had to add an index on the Name field on base element to make >> searches tolerable for users. I see that 8.1 does not have an index on the >> name field either, and figure I'm going to have to add it. We haven't >> loaded all of our CIs yet, so I can't test that aspect myself.**** >> >> ** ** >> >> Before I add the index, I wanted to make sure I'm not missing some new >> feature or something else that BMC might have done to improve performance >> when searching by CI name. Have you indexed the Name field, and if not, >> how's performance when searching by name (and how many rows/CIs do you >> have)?**** >> >> ** ** >> >> We have about 750,000 CIs. The database is SQL Server and the AR Servers >> are Windows. The full ITSM suite is installed.**** >> >> ** ** >> >> Thanks,**** >> >> Thad**** >> >> ** ** >> >> ** ** >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ **** >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
