RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: SQL
Expertise: Advanced
Jan 12, 2005



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Use the Connection String and SQL Profiler to Identify Your Application

Most of the time, OLEDB drivers to the underlying database support the ApplicationName property, which can be configured under the Advanced Tab. This property can be very useful when there are multiple applications running on a server and you need to track which application is issuing bad SQL.

Here's an example. In SQL Server, you've configured the Connection String using OLEDB Driver and set the ApplicationName to, say, "CTL." If you go to SQL Profiler and run a trace, you'll see all queries running which use the Connection String defined above, that appear with the Application Name of "CTL." You can henceforth filter the application specific queries and better troubleshoot the problem.

Akash Aggarwal
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date