{"id":6009,"date":"2022-08-17T08:44:13","date_gmt":"2022-08-17T08:44:13","guid":{"rendered":"https:\/\/pariswells.com\/blog\/?p=6009"},"modified":"2022-08-17T08:44:13","modified_gmt":"2022-08-17T08:44:13","slug":"automatic-tuning-azure-sql-drop-indexes","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/research\/automatic-tuning-azure-sql-drop-indexes","title":{"rendered":"Automatic tuning – Azure SQL Drop Indexes"},"content":{"rendered":"

Careful about enabling his , it can still report the duplicates and then the indexes can be evaluated to see if they are indeed duplicates. If they identical BTREE and INCLUDE and they are not supporting uniqueness or foreign key then they can be removed manually. Doesn\u2019t seem to be too many dups identified.<\/p>

In addition, if an index has not been used for 90 days or more then there is always a chance that there is a report (run 6 monthly or yearly) or end of year process that requires the index, in this case the index should be evaluated by the vendor before being dropped.<\/p>","protected":false},"excerpt":{"rendered":"

Careful about enabling his , it can still report the duplicates and then the indexes can be evaluated to see if they are indeed duplicates. If they […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[3902,3594,3903,591],"class_list":["post-6009","post","type-post","status-publish","format-standard","hentry","category-research","tag-automatic-tuning","tag-database","tag-drop-indexes","tag-sql"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t