David Klee shows the risk of creating custom indexes on third-party software:
The error file tells you specifically which indexes it does not like. The error file is found at:
C:\Users\(youraccount)\AppData\Local\Temp\vcsUpgrade\vcdb_req.err
You’ll find the error message towards the bottom of the document. My specific item was:
1 [42000](50000) [Microsoft][SQL Server Native Client 11.0][SQL Server]ERROR ! Extra indexes: VPX_EVENT.HFX_VPX_EVENT_Cover01; VPX_STAT_COUNTER.IX_VPX_STAT_COUNTER_STAT; VPX_TASK.HFX_VPX_TASK_Cover01;
For well-maintained third-party vendor software which doesn’t require you to add indexes to support the product at any scale beyond what a developer needs for basic testing, this isn’t an issue. And if you ever find that piece of software, write the company a note of congratulations for being the first…