All extractors for SQL databases are configured in the same way. See our tutorial for help.
After creating a new configuration and setting up database credentials, select which tables you want to import to KBC Storage.
If you prefer to write your own query to extract data to KBC Storage, use the Advanced Mode checkbox.
Please keep the following in mind when using the advanced mode:
Use as simple queries as possible. Avoid doing complex joins and aggregations. Remember that these queries are executed on the database server you are extracting from. This database system might not be designed or optimized for complex SELECT queries. Complex queries may result in timeouts, or they might produce unnecessary loads on your internal systems. Instead, import raw data, and then use KBC tools to give it the shape you want.
The MySQL database server also supports encrypting the whole database communication using SSL Certificates. See the official guide for instructions on setting it up.
An MS SQL Server instance hosted on Azure will normally have a host name such as
[srvName] is not an instance name, so the instance name should be left blank.
But the username needs to have the suffix
@[srvName] as in, for example,
When extracting data from a Snowflake database, the permissions must be set to allow the specified user to use the specified warehouse.
The following SQL code creates the role and user
KEBOOLA_SNOWFLAKE_EXTRACTOR and grants them access
MY_DATA database, and
Note that with the above setup, the user will not have access to newly created tables. You will either have to use a more permissive role or reset the permissions by calling: