In MS SQL, use the SQL Profiler Tool (came with SQL Server itself). In SapDB, put
dbalias="//yourservername/yourdatabasename?trace=c:/fileforlog.txt" (for *nix machines, use a relative or absolute path, or just use the name of the file: he will be on you app path). I think the best is the SapDB option, since it shows JDBC threads, connections, statements, prepared calls, parameters, results, method calls, but generate really big log files (in my app, a single hour user session sometimes generate a half Gb log file!). Best regards, Edson Richter ----- Original Message ----- From: Emmanuel Dupont To: 'OJB Users List' Sent: Tuesday, October 14, 2003 4:13 AM Subject: RE : How to get SQL statements executed by OJB without using P6Spy Hi Zhe, I think you have to find a database tool. Under MsSql we use Profil Gererator tool).... Check out with your database tools....... Good luck. -----Message d'origine----- De : Zhe Liu [mailto:[EMAIL PROTECTED] Envoy� : mardi 14 octobre 2003 04:17 � : [EMAIL PROTECTED] Objet : How to get SQL statements executed by OJB without using P6Spy Hi, I want to know the SQL statements executed by OJB, but I don't use ant and cannot run P6Spy. Can anybody tell me whether there is any way to get the real SQL statements? Thanks, Zhe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.525 / Virus Database: 322 - Release Date: 9/10/2003 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
