I want to troubleshoot some JDBC driver issues that occur in relationship with Microsoft SQL Server JDBC driver. How to set the right trace string in WebSphere Application Server to debug this scenario?

You can add com.ibm.ws.sqlserver.logwriter=all trace string to the default connection pooling trace string resulting in this string:

*=info:WAS.j2c=all:RRA=all:Transaction=all:WAS.database=all:com.ibm.ws.sqlserver.logwriter=all

More information can be find in:

JDBC trace configuration
https://www.ibm.com/docs/en/was/9.0.5?topic=problems-jdbc-trace-configuration

If you want to find out more about internal MS-SQL jdbc driver processing mechanisms you can use com.microsoft.sqlserver.*=all trace string, resulting trace string is:

*=info:WAS.j2c=all:RRA=all:Transaction=all:WAS.database=all:com.microsoft.sqlserver.*=all

Both trace strings can be combined to get more detailed information:

*=info:WAS.j2c=all:RRA=all:Transaction=all:WAS.database=all:com.ibm.ws.sqlserver.logwriter=all:com.microsoft.sqlserver.*=all

------------------------------
Marcio D'Amico
------------------------------