Need consultation for the next question...
I have large n-tier buisiness application, working with database with Linq-To-Entities (EDM). Every one from several hundreds of my WCF-methods create own new EMD context when invoked. To help developers tracking of requests via Profiler, i wrote some extension method for EntityConnection, that split and join again connection string before open connection, replacing default Application Name to custom one, passed as parameter (so, i use unique method name as application name in every case). It works great, now i can use mane of every method to track with Profiler only it`s calls, and without filter by Applicaiton Name i can see online in Profiler what methods was invoked in system right now.
But, i still have a one question. As fas as i discovered, connection pooling is also based on something like connection string, so it would be good to get consultation: does my extension method affect anyway on SQL Server Performance or not? Is there any conflict with connection pooling or not?