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

从 src/Microsoft/SqlServer/Management/SqlEnum/PostProcessTable.cs 第 81-83 行附近开始，检查获取 Table SMO 对象时使用的查询路径。重现或跟踪表扫描记录行为，然后验证未使用索引检测不再将此元数据查询视为索引使用。