Concept | Connections to SQL databases#
Watch the video
Dataiku provides varying levels of support for connections to SQL databases. These support levels include full support, limited support, and no support. For the latest details on database support, be sure to check the reference documentation.
For unsupported databases, connections from Dataiku are still possible by using the appropriate Java Database Connectivity (JDBC) drivers. In such cases, reading from the database often works, but it is rare that writing to the database would work without some further configuration.
Apart from reading and writing datasets in SQL databases, Dataiku can leverage in-database computation when rendering charts, executing visual recipes, and executing SQL code recipes. Leveraging the SQL execution engine can speed up computation!
Defining a connection#
Setting up a connection to an SQL database involves two main steps. First, install the JDBC driver for your database into the Dataiku data directory by copying the driver’s JAR file (and any dependencies) to the
DATA_DIR refers to the data directory where Dataiku is installed.
Next, from the Administration section of the Dataiku homepage, a user with admin rights can create a new connection by going to the Connections tab, selecting the appropriate connection type (for the particular SQL database), and filling in parameter values such as the database name, host, port, user, and password.
The admin can also define other settings like authentication mode or permissions for user groups on this connection. For example, the admin can grant the data team permission to read only or to read and write from this connection.
Once permissions have been given, and the connection has been set up and tested, you can return to your project and import datasets from this SQL connection. You can do this by selecting the table that you want to import from the list of tables in the datable and creating the dataset.
For more information about connecting to SQL databases, see SQL databases in the reference documentation.