Lesson Learned #74: The importance of having the Application Name configured in connection string

This post has been republished via RSS; it originally appeared at: Azure Database Support Blog articles.

Hello Team,

Many, many times, we saw service requests that our customers need to identify who runs a specific query but, even after enabling the SQL Auditing feature, in Azure SQL Database they are not able to identify who/which is the application that did it.

Why? because they didn't specify an application name in the connection string.

Yes, I know that we have the IP address, the process id, etc.., but in a distributed environment that we have, using the application name would be very simply to identify which is the application that is doing something and what.

So, if you don't specify the Application Name, the client will use the driver name and it will be the same for multiple applications. For this reason, I strong recommend to change your application name setting in your connection string, for better identification of your application. Please, follow this URL.


REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.