You can tell DPA to exclude SQL statements for a particular SQL hash. So right after you start your profiler or tuning adviser, if you are getting a consistent hash for the activity, you could tell DPA to ignore it henceforth by running the following T-SQL against your repository database.
INSERT INTO con_qp_exclude VALUES (<DBID>, 'H','<HASHGOESHERE>','S');
Just replace the DBID with the ID from SELECT ID, NAME FROM COND where name = <INSTANCENAMEQUERYEXISTS>. Then place the hash of the query you want to exclude in <HASHGOESHERE>.
But if you have already collected the data, that’s not going to help. And if the hash changes, it also won’t help. You might also consider using the monitoring blackout feature but then you will then, of course, not be logging any data.