When trying to use the ODBC to extract data from table ldap_import, the table is not found. - Support and Troubleshooting

When trying to use the ODBC to extract data from table ldap_import, the table is not found. Issue  Symptoms When the ODBC driver connects to a ServiceNow instance, it us unable to retrieve data from import sets tables such as 'ldap_import'.

Release All ODBC releases

Cause This is by design. The odbc driver uses a large memory overhead to consume all tables in the ServiceNow instance. This happens upon connection and can make the connection take a bit longer. To help this, Dev designed the driver to not consume all tables and eliminates import set tables and system tables.

Resolution There are some tables that the instance blocks from being consumed in schema list.

The following tables are not accessible:

tables where ACLs do not provide read access tables that are on rotation extension import set tables tables that begin with "ecc_", "sysx_" and "ts_" Since the ldap_import table is an extension of Import Set Row, it's also excluded.

However, you can set the driver up to access these tables by doing the following:

Go to the Microsoft DSN entry for the ServiceNow odbc driver. On the Custom Properties field, change the value from: url=https:// .service-now.com to: url=https:// .service-now.com;EnableDBSchema=false Reconnect to the DSN with your reporting tool, IE: Excel or ISQL or SQL Linked Server. Validate you are able to report on the 'ldap_import' table. Note : Notes are added to emphasize points, remind users of something, or indicate minor problems that could arise as a result of executing the steps in the article.

Warning : A warning should be used when corruption, data loss, or downtime is possible if instructions are not obeyed.