Diagnosing problems with the JDBC driver
No matter how well an application is designed and developed, problems will inevitably occur. When they do, it's important to have some techniques for diagnosing those problems. When using the Microsoft JDBC Driver for SQL Server, some common problems that can occur aren't having the right driver version or being unable to connect to a database.
The articles in this section discuss many techniques for diagnosing these and other problems including error handling, checking the driver version, tracing, and troubleshooting connectivity issues.
In this section
| Article | Description |
|---|---|
| Handling errors | Describes how to handle errors that are returned from SQL Server. |
| Getting the driver version | Describes how to determine which version of the JDBC driver is installed. |
| Tracing driver operation | Describes how to enable tracing when using the JDBC driver. |
| Troubleshooting connectivity | Describes how to troubleshoot database connectivity. |
| Accessing diagnostic information in the extended events log | Describes how to use information in the server's extended events log to understand connection failures. |
See also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for