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.