Determining if your ODBC driver is working correctly
- Cannot connect to the instance
- Error message received during processing
- Queried information lost
- Connection dropped
The ODBC driver may not appear to be working correctly because too many records are being pulled in a query, there are missing ACLs, or a 3rd party application is interfering with the query.
First, test the ODBC driver. To do this, create the system DSN in the ODBC driver and click the Test Connection button. Details on how to test the ODBC Driver can be found here.
Try running a test query that returns only one record from a table, such as a single incident. To do this, run select short_description from incident where number=‘<existing_incident_number>’; and put the incident number you are sure exists on your instance instead of <existing_incident_number>. This shows if the driver is running correctly, regardless of ACL issues or number of records.
|Note: The ODBC driver is not designed to pull a lot of data at a time, so any queries you run should account for this.|
If testing a single record does not work, try running the same query and excluding 3rd party applications.
To determine if the ODBC driver is working correctly by excluding 3rd party applications, follow these steps:
- Open ISQL (this comes with the ServiceNow ODBC Driver).
- Connect to the instance using the steps identified in Running Interactive SQL (ODBC) in the ServiceNow product documentation.
- If you have special characters in your username or password, use the following:
Customconnect "DSN=your_dsn_name; UID=username;PWD=password"
- Issue a SELECT statement to retrieve the records you are pulling in through your specific application.