Not able to access data registered in Unity Catalog using Simba ODBC driver

[FelipeRegis]

Hi folks, 

I'm working on a project with Databricks using Unity Catalog and a connection to SSIS (SQL Server Integration Services).

My team is trying to access data registered in Unity Catalog using Simba ODBC driver version 2.8.0.1002. They mentioned they can connect but catalog and metadata does not appear.

They mentioned Unity Catalog doesn't allow DSN connection and that this is the type of connection being used currently. Follows documentation used from Alteryx Databricks Unity Catalog.

I'm looking for alternatives and possible cause of this problem.

It follows print with configurations used:

Does anybody can help?

Thanks in advance.

Felipe Regis.

[Kaniz_Fatma]

Hi @FelipeRegis, It seems you’re encountering issues with accessing data registered in Unity Catalog using the Simba ODBC driver.

Let’s explore some possible solutions:

1. Delta Lake Native Connector:

   • Consider using Delta Lake’s native Delta JDBC/ODBC connector instead of a third-party ODBC driver like Simba. The native connector is optimized for Delta Lake and supports bulk inserts, which can significantly ...¹.
   • Use the Delta Lake bulk insert API to load data in batches instead of inserting one record at a time.

2. HTTPS and SSL Options:

   • Ensure that you’ve correctly configured the HTTPS and SSL options in your connection settings.
   • For HTTPS, obtain the HTTP Path from your Databricks connection details.
   • For SSL, enable SSL and use the system trust store².

3. Simba ODBC Driver Version:

   • To access data registered in Unity Catalog over ODBC, use Simba ODBC driver version 2.6.19 or above³.
   • Make sure you’re using a compatible version of the Simba driver.

4. Check Installation and Permissions:

   • Verify that the Simba ODBC driver is properly installed on your system.
   • Ensure that the user account connecting to Unity Catalog has the necessary permissions to access metadata and catalog information.

5. Debugging and Logs:

   • Check the logs for any error messages or warnings related to the ODBC connection.
   • Enable verbose logging if possible to get more detailed information about the issue.

Remember to test each step thoroughly to identify the root cause of the problem. 

Good luck with your project! 😊