Home
%3CLINGO-SUB%20id%3D%22lingo-sub-481047%22%20slang%3D%22en-US%22%3ELesson%20Learned%20%2374%3A%20The%20importance%20of%20having%20the%20Application%20Name%20configured%20in%20connection%20string%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481047%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Team%2C%3C%2FP%3E%0A%3CP%3EMany%2C%20many%20times%2C%20we%20saw%20service%20requests%20that%20our%20customers%20need%20to%20identify%20who%20runs%20a%20specific%20query%20but%2C%20even%20after%20enabling%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsql-database%2Fsql-database-auditing%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ESQL%20Auditing%3C%2FA%3E%20feature%2C%20in%20Azure%20SQL%20Database%20they%20are%20not%20able%20to%20identify%20who%2Fwhich%20is%20the%20application%20that%20did%20it.%3C%2FP%3E%0A%3CP%3EWhy%3F%20because%20they%20didn't%20specify%20an%20application%20name%20in%20the%20connection%20string.%3C%2FP%3E%0A%3CP%3EYes%2C%20I%20know%20that%20we%20have%20the%20IP%20address%2C%20the%20process%20id%2C%20etc..%2C%20but%20in%20a%20distributed%20environment%20that%20we%20have%2C%20using%20the%20application%20name%20would%20be%20very%20simply%20to%20identify%20which%20is%20the%20application%20that%20is%20doing%20something%20and%20what.%3C%2FP%3E%0A%3CP%3ESo%2C%20if%20you%20don't%20specify%20the%20Application%20Name%2C%20the%20client%20will%20use%20the%20driver%20name%20and%20it%20will%20be%20the%20same%26nbsp%3Bfor%20multiple%20applications.%20For%20this%20reason%2C%20I%20strong%20recommend%20to%20change%20your%20application%20name%20setting%26nbsp%3Bin%20your%20connection%20string%2C%20for%20better%20identification%20of%20your%20application.%20Please%2C%20follow%20this%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fapi%2Fsystem.data.sqlclient.sqlconnection.connectionstring%3Fview%3Dnetframework-4.7.2%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EURL.%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EEnjoy!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-481047%22%20slang%3D%22en-US%22%3E%3CP%3EMany%2C%20many%20times%2C%20we%20saw%20service%20requests%20that%20our%20customers%20need%20to%20identify%20who%20runs%20a%20specific%20query%20but%2C%20even%20after%20enabling%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsql-database%2Fsql-database-auditing%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ESQL%20Auditing%3C%2FA%3E%20feature%2C%20in%20Azure%20SQL%20Database%20they%20are%20not%20able%20to%20identify%20who%2Fwhich%20is%20the%20application%20that%20did%20it.%3C%2FP%3E%0A%3CP%3EWhy%3F%20because%20they%20didn't%20specify%20an%20application%20name%20in%20the%20connection%20string.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E

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.

Enjoy!