Hello,
We are monitoring the activities on our services exposed by sqlserver to know who is using what. It helps us to make decision on how/when to upgrade views and storedprocs based on usage and also to troubleshoot incidents.
In our environment, other than users using the services (views and storedproc), we have many BizTalk applications that also consume the services. In the reporting tool (a cube), we can see service consumption by servicename/user/application/hostname/time and all.
However, BizTalk Server has separate hosts using the same credentials and application sharing the same hosts. Thus, in the reporting tool, one cannot determine which BizTalk application port is using that specific service since they all have the same loginame and program_name on the sql server side (see master.sys.sysprocesses view).
We could review our host configuration and add hosts with different credentials and assign them to the rcv or snd ports. But this path can quickly becomes a configuration hell (declaring host, add hosts instances, assign adapters to hosts, review host distribution by ports and ...)
Instead, our DBA ask us to modify/add the "Application Name" keyword in the connection string and assign the BizTalk application name. Sounds easy. Unfortunately, this keyword is not accessible from WCF-SQL binding. Strangely, the WorkstationId, another connection string keyword, can be set from the bindings. But it is somehow wrong to use it for something other than hostname. And it would look awkward in the reports.
So, is there a way to modify and add the applicationname keyword in the connection string of a WCF-SQL adapter (BizTalk Adapter Pack 2.0 CU5)? I did investigate and review Microsoft.Adapters.SQL code. I cannot understand the relation between WCF Channel and SqlAdapterConnectionUri classes. The latter seem the place where to intervene. But it may already to deep down into the mechanism.
And why WorkstationId is in the binding and not ApplicationName? To me, it make more sense to customize the AppName and not the hostname, right?
Thanks,
Etienne
