Obtaining Table SMO object causes table scan to be recorded

I'm not sure what the fix is here, but, that CASE statement does not short-circuit. Even if the IF condition is true, it still executes the subquery in the ELSE clause.

This means a table scan on one of the indexes (or heap) is recorded.

In most cases, this is probably not a big deal...but if you're using SMO objects to create backup scripts for unused indexes you are getting ready to drop...it's kind of a problem when all of a sudden SMO starts using those unused indexes, causing them to be excluded from the unused index detection queries.

https://github.com/microsoft/sqlmanagementobjects/blob/d6f3e68fe6fae09d22355a160baa525d8032fd64/src/Microsoft/SqlServer/Management/SqlEnum/PostProcessTable.cs#L81-L83

Commencez dans src/Microsoft/SqlServer/Management/SqlEnum/PostProcessTable.cs autour des lignes 81-83 et examinez le chemin de requête utilisé lors de l’obtention d’un objet Table SMO. Reproduisez ou suivez le comportement d’enregistrement des analyses de table, puis vérifiez que la détection des index inutilisés ne considère plus cette recherche de métadonnées comme une utilisation d’index.