# Parameterized queries are counted as duplicates

**URL:** <https://community.miniprofiler.com/t/parameterized-queries-are-counted-as-duplicates/97>\
**Category:** uncategorized\
**Created:** [July 25, 2012, 3:41am UTC](https://community.miniprofiler.com/t/parameterized-queries-are-counted-as-duplicates/97 "2012-07-25T03:41:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dshook](https://sea2.discourse-cdn.com/flex016/user_avatar/community.miniprofiler.com/dshook/32/1024_2.png) [@dshook](https://community.miniprofiler.com/u/dshook)\
**Post date:** [July 25, 2012, 3:41am UTC](https://community.miniprofiler.com/t/parameterized-queries-are-counted-as-duplicates/97/1 "2012-07-25T03:41:07Z")

</div>

A query that’s called with different parameters should not be counted as a duplicate. This happens very frequently with linq2sql which calls the same query repeatedly with different parameters.

A related enhancement would be to show the parameters that are used for each query.

---

<div class="post-metadata">

**Author:** ![Keith](https://sea2.discourse-cdn.com/flex016/user_avatar/community.miniprofiler.com/keith/32/1029_2.png) [@Keith](https://community.miniprofiler.com/u/Keith)\
**Post date:** [July 26, 2012, 7:05am UTC](https://community.miniprofiler.com/t/parameterized-queries-are-counted-as-duplicates/97/2 "2012-07-26T07:05:41Z")

</div>

Actually they really should. The duplicate functionality is mainly to identify N+1 issues (which, as you say, Linq2SQL is very prone to) and they have exactly that pattern.

[Read more on StackOverflow](http://stackoverflow.com/questions/97197/what-is-the-n1-selects-problem).