About SQL Server JDBC logging

During troubleshooting, Guidewire might request a trace log from the Microsoft JDBC driver. Do not turn on trace logging in other circumstances as it places a heavy overhead on the system, and the files created can quickly become very large.

It is possible to turn on Microsoft JDBC driver logging at PolicyCenter startup by specifying the jdbc-trace-file and jdbc-trace-level attributes on the <sqlserver-settings> element:

<database ...>
  <sqlserver-settings jdbc-trace-file="file name" jdbc-trace-level="trace level" />
  ...
</database>

The trace level is a string that corresponds to a valid trace level as documented at the following Microsoft site:

http://msdn.microsoft.com/en-us/library/ms378517(SQL.90).aspx?ppud=4

If you do not specify the location of the trace file, it defaults to the following location:

C:/temp/msjdbctrace%u.log

Refer to the following web site for documentation on the trace file specification:

http://docs.oracle.com/javase/1.5.0/docs/api/java/util/logging/FileHandler.html

Using %h and %t puts the file in the Documents and Settings directory under the name which is running the application server.

Guidewire provides a means to manage JDBC Driver logging in the PolicyCenter Server Tools Info Pages > Microsoft JDBC Driver Logging screen. Use this screen to start and stop Microsoft driver logging on a running application server. Using this screen is a better option if tracing a particular operation, in order to minimize system impact and size of the trace file.