>From what I can tell of the table you provided -- none of the indexes are being used.
So - deleting them would have no affect. Except (and this is a stretch) ... not having these indexes exist means more memory available to put other indexes into memory. (But - I doubt that is an issue here). (If they are not being used - they wouldn't be in memory anyway) Deleting these indexes will improve "insert and update performance" ... but - with the speed of disks these days - I doubt that is your bottleneck. My general recommendation is to "update statistics", identify the problem queries -- and "create indexes" to assist. General question ... has anybody seen deleting an index (or 10 indexes) actually improve any query performance? If so -- how did it improve? -John On Fri, May 29, 2015 at 2:31 AM, Madhu V <[email protected] > wrote: > ** > > Recently while troubleshooting performance issues on our Production > system, our DBA team has identified some unused indexes on T2356 (HPD:Help > Desk form) and suggested us removing them could improve the query > performance and clean up some space in the Database. We have verified the > same from remedy end and found many are OTB defined indexes for the form , > same have been mentioned below. Please suggest us whether can we go ahead > and remove these indexes ? Please mention if you foresee any impacts. > > > > *TableName* > > *IndexName* > > *Remedy Form Name* > > *Remedy Field Name* > > *UserSeek* > > *UserScans* > > *UserLookups* > > *UserUpdates* > > *TableRows* > > T2356 > > I2356_200000003_1 > > HPD:Help Desk > > Product Categorisation Tier 1 > Product Categorisation Tier 2 > Product Categorisation Tier 3 > > 0 > > 0 > > 0 > > 105264 > > 903085 > > T2356 > > I2356_240001002_1 > > HPD:Help Desk > > Product Name > > 0 > > 0 > > 0 > > 105264 > > 903085 > > T2356 > > I2356_1000000869_1 > > HPD:Help Desk > > Incident Association Type > > 0 > > 0 > > 0 > > 103974 > > 903085 > > T2356 > > I2356_301735100_1 > > HPD:Help Desk > > mc_ueid > > 0 > > 0 > > 0 > > 102675 > > 903085 > > T2356 > > I2356_301734000_1 > > HPD:Help Desk > > Component_ID > > 0 > > 0 > > 0 > > 102675 > > 903085 > > T2356 > > I2356_250000023_1 > > HPD:Help Desk > > Escalated? > > 0 > > 248 > > 0 > > 102716 > > 903085 > > > > Please find the version and configuration of AR System details below: > > Server version : 8.1.00 201409181335Hotfix > > Mid-Tier Version : 8.1.01 (SP1) 201408220302 Hotfix > > Web Server Information : Apache Tomcat/7.0.55 Operating System Name : > Windows Server 2012 > > Java Version : 1.7.0_45 > > Server Group : Yes > > DB : MS SQL 2012 > > On Thu, May 28, 2015 at 6:20 PM, John Sundberg < > [email protected]> wrote: > >> ** >> Well - if it is a unique index - you will make swiss cheese of your >> system. >> >> I would suggest - don’t delete the index. >> >> I will ask you a question in return: >> >> What benefits do you see in removing an OTB index? >> >> -John >> >> On Thu, May 28, 2015 at 4:07 AM, Madhu V < >> [email protected]> wrote: >> >>> Hi , >>> >>> Can you please let me if there will be any impact if we remove the OTB >>> defined indexes from the OTB form? >>> >>> Regards >>> Madhu >>> >>> >>> _______________________________________________________________________________ >>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >>> "Where the Answers Are, and have been for 20 years" >>> >> >> >> >> -- >> >> *John Sundberg* >> Kinetic Data, Inc. >> "Your business. Your process." >> >> 651-556-0930 I [email protected] >> www.kineticdata.com I community.kineticdata.com >> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> > > _ARSlist: "Where the Answers Are" and have been for 20 years_ -- *John Sundberg* Kinetic Data, Inc. "Your business. Your process." 651-556-0930 I [email protected] www.kineticdata.com I community.kineticdata.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
