At some client sites, connecting CaseTalk to the SQL Server repository can take several seconds, and it is not clear where that time goes.

Starting CaseTalk with the /SQLTRACE command line switch now records what happens during a connect. Two files are written next to the CaseTalk settings file:

• a connection log listing each step of the connect (loading the database driver, the login itself, detecting the database version, reading the server settings and statistics, and the user login) with the number of milliseconds each step took
• a full SQL trace of every statement sent to the server, with millisecond timestamps

The log also records when a connection is lost and re-established, which explains delays that appear in the middle of a session rather than at startup. No passwords are written, so the files can be mailed to support.

This makes it possible to tell whether the delay is caused by the network and database driver, by the server, or by the work CaseTalk itself performs directly after connecting.