Using JDBC data sources

Using the driver : Tracking JDBC calls with DataDirect Spy : Enabling DataDirect Spy : Using JDBC data sources

You can use DataDirect Spy to track JDBC calls made by a running application with either of these features:

JNDI for Naming Databases

Connection Pooling

The com.ddtek.jdbcx.SQLServer.SQLServerDataSource class supports setting a semi-colon separated list of DataDirect Spy attributes.

Windows example

SQLServerDataSource sds = new SQLServerDataSource();
sds.setDescription("My SQLServer Datasource");
sds.setServerName("MyServer");
sds.setPortNumber(1433);
sds.setUser("User123");
sds.setPassword("secret");
sds.setDatabaseName("MyDB");
sds.setSpyAttributes("log=(file)C:\\temp\\spy.log;logIS=yes;logTName=yes");
Connection conn=sds.getConnection;
...

Note: If coding a path on Windows to the log file in a Java string, the backslash character (\) must be preceded by the Java escape character, a backslash. For example: log=(file)C:\\temp\\spy.log;logIS=yes;logTName=yes.

DataDirect Spy loads the driver and logs all JDBC activity to the spy.log file located in the C:\temp directory (log=(file)C:\\temp\\spy.log). In addition to regular JDBC activity, the spy.log file also logs activity on InputStream and Reader objects (logIS=yes). It also includes the name of the current thread (logTName=yes).

UNIX example

SQLServerDataSource mds = new SQLServerDataSource();
mds.setDescription("My SQLServer Datasource");
mds.setServerName("MyServer");
mds.setPortNumber(1433);
mds.setUser("User123");
mds.setPassword("secret");
mds.setDatabaseName("MyDB");
mds.setSpyAttributes("log=(file)/tmp/spy.log;logIS=yes;logTName=yes");
Connection conn=mds.getConnection;
...

DataDirect Spy loads the driver and logs all JDBC activity to the spy.log file located in the /tmp directory (log=(file)/tmp/spy.log). In addition to regular JDBC activity, the spy.log file also logs activity on InputStream and Reader objects (logIS=yes). It also includes the name of the current thread (logTName=yes).