![]() |
VOOZH | about |
You can use the SQL Gateway to configure a TDS (SQL Server) remoting service and set up a linked server for Lakebase data. After you have started the service, you can use the UI in SQL Server Management Studio or call stored procedures to create the linked server. You can then work with Lakebase data just as you would a linked SQL Server instance.
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
To connect to Databricks Lakebase, start by setting the following properties:To authenicate using OAuth client credentials, you need to configure an OAuth client in your service principal. In short, you need to do the following:
For more information, refer to the Setting Up OAuthClient Authentication section in the Help documentation.
To authenticate using the OAuth code type with PKCE (Proof Key for Code Exchange), set the following properties:
For more information, refer to the Help documentation.
See the SQL Gateway Overview for a guide to configure a TDS remoting service in the SQL Gateway UI. The TDS remoting service is a daemon process that listens for TDS requests from clients.
After you have configured and started the daemon, create the linked server and connect. You can use the UI in SQL Server Management Studio or call stored procedures.
Follow the steps below to create a linked server from the Object Explorer.
Data Source: Enter the host and port the TDS remoting service is running on, separated by a comma.
Note that a value of "localhost" in this input refers to the machine where SQL Server is running so be careful when creating a linked server in Management Studio when not running on the same machine as SQL Server.
In addition to using the SQL Server Management Studio UI to create a linked server, you can use stored procedures. The following inputs are required:
datasrc: The host and port the service is running on, separated by a comma.
Note that a value of "localhost" in the datasrc input refers to the machine where SQL Server is running, so be careful when creating a linked server in Management Studio when not running on the same machine as SQL Server.
Call sp_addlinkedserver to create the linked server:
EXEC sp_addlinkedserver @server='Lakebase', @provider='MSOLEDBSQL', @datasrc='< MachineIPAddress >,1434', @catalog='CData Lakebase Sys', @srvproduct=''; GO
Call the sp_addlinkedsrvlogin stored procedure to allow SQL Server users to connect with the credentials of an authorized user of the service. Note that the credentials you use to connect to the service must specify a user you configured on the Users tab of the SQL Gateway.
EXEC sp_addlinkedsrvlogin @rmtsrvname='Lakebase', @rmtuser='admin', @rmtpassword='test', @useself='FALSE', @locallogin=NULL; GO
SQL Server Management Studio uses the SQL Server Client OLE DB provider, which requires the ODBC driver to be used inprocess. You must enable the "Allow inprocess" option for the SQL Server Native Client Provider in Management Studio to query the linked server from SQL Server Management Studio. To do this, open the properties for the provider you are using under Server Objects -> Linked Servers -> Providers. Check the "Allow inprocess" option and save the changes.
You can now execute queries to the Lakebase linked server from any tool that can connect to SQL Server. Set the table name accordingly:
SELECT * FROM [linked server name].[CData Lakebase Sys].[Lakebase].[Orders]👁 The result of a query in SQL Server Management Studio. (Salesforce is shown.)
Download a free trial of the Lakebase ODBC Driver to get started:
Download NowLearn more:
👁 Lakebase IconThe Lakebase ODBC Driver is a powerful tool that allows you to connect with live data from Lakebase, directly from any applications that support ODBC connectivity.
Access Lakebase data like you would a database - read, write, and update Lakebase 0, etc. through a standard ODBC Driver interface.