November 19, 2003 at 2:16 am
hi,
Is there any way that you can do a per application odbc trace,without changing code (ie can it be configured somewhere)? Anyonebode had success in creating a custom trace dll?
Thnx
Ruan
November 24, 2003 at 12:00 pm
This was removed by the editor as SPAM
December 2, 2003 at 8:38 am
quote:
Is there any way that you can do a per application odbc trace,without changing code (ie can it be configured somewhere)? Anyonebode had success in creating a custom trace dll?
Hello Ruan,
No. ODBC doesn't support seperating the commands in a trace by session or app, TTBOMK. It sounds like you have more than one application on the "failing machine" and you need to differentiate which commands are coming from which application. Since ODBC is used primarily for client-server applications, you should be able to install your client on a test machine and trace from there (assuming you can recreate the error on another workstation). If not, take a look at the version of MDAC and the version of the drivers you are using on that machine (other apps may have installed drivers that are older).
If the problem is that you can't install a test machine with the version of the OS that is running on that pc, consider investing in VMWare, which will allow a single machine to run dozens of different versions of the OS and configurations of software, allowing you more flexibility in testing.
HTH,
--- Nick Malik
December 3, 2003 at 11:22 am
Unless you have a ton of SQL servers and don't know which one(s) it's using, SQL profiler may be helpful.
It has the capacity to record/show all SQL statements issued. You could try filtering by host/db/appname.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply