Strictly speaking no, we don't support direct modification of the db unless directed by Support. (You'd be amazed at some of the... interesting modifications we've found in customer databases in the past )
Can I ask - which indexes are you interested in removing, and why?
Thanks for the quick reply. I certainly understand what you mean!
The number one candidates for me to remove are the following four indexes, all on the EPONotificationLog table:
Next up are these two on EPOEvents:
I show that these indexes have not been used by any seeks, scans or lookups in the past two months, but they have been updated nearly 60 million times.
That is a lot of unnecessary work being done as these events are inserted and deleted. If I can avoid that it would make me a very happy DBA.
TableName IndexName user_seeks user_scans user_lookups user_updates last_user_seek last_user_scan last_user_lookup last_user_update EPONotificationLog IX_EPONotificationLog_NotificationRuleName 0 0 0 13,398,780 NULL NULL NULL 4/28/10 12:14 PM EPONotificationLog IX_EPONotificationLog_BranchNodePath 0 0 0 13,398,780 NULL NULL NULL 4/28/10 12:14 PM EPONotificationLog IX_EPONotificationLog_NotificationType 0 0 0 13,398,780 NULL NULL NULL 4/28/10 12:14 PM EPONotificationLog IX_EPONotificationLog_Status 0 0 0 13,398,780 NULL NULL NULL 4/28/10 12:14 PM EPOEvents IX_EPOEvents_AutoGUID 0 0 0 1,950,529 NULL NULL NULL 4/28/10 12:14 PM EPOEvents IX_EPOEvents_ReceivedUTC 0 0 0 1,950,529 NULL NULL NULL 4/28/10 12:14 PM
That's a little strange. Do you not use the notifications system or run any event-based reports?
I'll have to ask about the reporting. I can tell you that the only indexes that get any use on the EPONotificationLog table are the following:
PK_EPONotificationLog 6695943 seeks
IX_EPONotificationLog_Priority 6710 scans
IX_EPONotificationLog_TimeNotificationSent 3926 seeks
Note that this activity is over a two month period.
Any more thoughts on this issue? I am told that we do reporting, but mostly on demand.
I think the best bet is to remove the indexes and watch performance, but I don't want to negate any SLAs, etc..
I think this is being worked in parallel - someone asked your question on one of the internal lists, and got a reply from one of the senior developers
The EPONotificationLog indexes have been removed in ePO 4.5
The EPOEvents indexes should *NOT* be removed under any circumstances
He seemed fairly emphatic about it