When I am working on some project, it is normal to need to analyze the queries that are executed on the database to detect a possible bug or something that is not matched with what I expected.
For this, SQL Server Profiler gives me a good and quick overview of what is being requested for each connection to the database.
The case of a registration in the profiler can be shown as:
As can be seen in the Application Name column has the value ".Net Sql Client Data Provider", which makes it very difficult in filtering to only the application that we intend to analyze the data.
To avoid this, we only need to indicate on ConnectionString, the name of our application, and everything gets easier.
"Data Source=localhost;Initial Catalog=MyDatabase;
Integrated Security=True;Application Name=MyAppName"
After that, we get something more friendly like:
