A customer discovered that their application was passing in a data type that didn't match the column definition in their SQL Server table. This caused an implicit conversion (CONVERT_IMPLICIT) on that column, which prevented the query optimizer from using the existing index — forcing a full clustered index scan across a 10 million row table. DPA's Table Tuning Advisor surfaced this problem clearly.
The customer then wanted to know whether DPA could search for other occurrences of CONVERT_IMPLICIT across their workload. The attached query does exactly that: it searches saved plans in the DPA repository for a specified instance and time window, identifying every occurrence. The results return the DPA SQL and plan hash values ranked by duration — feed those into DPA's Find SQL feature to review each affected statement.
Note: since this query is searching through SQL Server plan XML, it may take a minute or more to complete.