As a follow-up of my post yesterday where I talked about a production issue we had with one of services, I want to share a tip that can make debugging more enjoyable
I explained how you can use the built-in reports to investigate possible problems. Here is the report I shared yesterday:
You see that it mentions a Session ID but it doesn’t gives you any clue about the exact application.
To map the Session ID to a specific application, you should update your SQL Server connection string with an Application Name property:
Server=myServerAddress;Database=myDataBase;Trusted_Connection=True;Application Name=myApplicationName:
If you know look at the same report, the Login Name column is updated with the application name:
You can now also use this information in for example a stored procedure through the following command:
SELECT APP_NAME();