User Tools

Site Tools


connectors

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
connectors [2023/11/02 08:13] – [Security considerations] dmitryconnectors [2024/01/28 15:46] dmitry
Line 32: Line 32:
 |SQL Server / Azure SQL Database    |ODBC / Native  |Bulk export supported (only for the native driver) | |SQL Server / Azure SQL Database    |ODBC / Native  |Bulk export supported (only for the native driver) |
 |Oracle            |ODBC / Native  | | |Oracle            |ODBC / Native  | |
-|MySQL            |ODBC / Native  | |+|MySQL            |ODBC / Native  |Bulk export supported. |
 |PostgreSQL    |ODBC / Native  |Bulk export supported (only for the native driver). Tested with versions 10,12, and 15 | |PostgreSQL    |ODBC / Native  |Bulk export supported (only for the native driver). Tested with versions 10,12, and 15 |
 |MariaDB           |ODBC / Native  | | |MariaDB           |ODBC / Native  | |
Line 38: Line 38:
 |Amazon Redshift   |ODBC / Native  | | |Amazon Redshift   |ODBC / Native  | |
 |Snowflake         |ODBC / Native  |Bulk export supported (only for the ODBC driver) | |Snowflake         |ODBC / Native  |Bulk export supported (only for the ODBC driver) |
 +|Google BigQuery   |ODBC only  |Bulk export is supported. |
 |MS Access         |ODBC only  | | |MS Access         |ODBC only  | |
 |Amazon Athena     |ODBC only  | | |Amazon Athena     |ODBC only  | |
Line 44: Line 45:
 |Exasol            |ODBC only  | | |Exasol            |ODBC only  | |
 |SAP HANA          |ODBC only  | | |SAP HANA          |ODBC only  | |
 +|Sybase IQ         |ODBC only  | |
 |Vertica           |ODBC only  | | |Vertica           |ODBC only  | |
-|Apache Hive       |ODBC only  |Only import via visual queries and custom SQL | +|Apache Hive       |ODBC only  |Import via visual queries only, custom SQL statements.
-|Google BigQuery   |ODBC only  |Only import via visual queries and custom SQL +|Denodo            |ODBC only  |Import via visual queries only, custom SQL statements.|
-|Denodo            |ODBC only  | |+
 |Databricks        |ODBC only  | | |Databricks        |ODBC only  | |
 |Generic SQL:2003  |ODBC only  |Custom SQL only | |Generic SQL:2003  |ODBC only  |Custom SQL only |
Line 80: Line 81:
   * [[connectors:awss3|Amazon S3]]   * [[connectors:awss3|Amazon S3]]
   * [[connectors:azureblobstorage|Azure Blob Storage]]   * [[connectors:azureblobstorage|Azure Blob Storage]]
 +  * [[connectors:chatgpt|ChatGPT]]
   * [[connectors:dropbox|Dropbox]]   * [[connectors:dropbox|Dropbox]]
   * [[connectors:googleanalytics|Google Analytics]]   * [[connectors:googleanalytics|Google Analytics]]
Line 96: Line 98:
   * In connectors, use read-only accounts and don't expose unnecessary objects (e.g. schemas, tables, etc.)   * In connectors, use read-only accounts and don't expose unnecessary objects (e.g. schemas, tables, etc.)
   * Don't use embedded connectors for accessing sensitive information because they can be easily copied unless dynamic authentication is used (such as "Windows integrated")   * Don't use embedded connectors for accessing sensitive information because they can be easily copied unless dynamic authentication is used (such as "Windows integrated")
-  * Keep in mind that users may write and execute custom SQL queries/statements using connectors without knowing the credentials stored in the connectors+  * Keep in mind that users may perform various operations (e.g. write and execute custom SQL queries/statementsusing connectors without knowing the credentials stored in the connectors
   * SQL-related actions (such as "Import from database") and commands (such as "Custom SQL statement") insert [[parameters]] as plain text into the generated SQL statement which can make them vulnerable to SQL injection. Don't use parameters in such actions when parameter values can't be trusted or sanitized.   * SQL-related actions (such as "Import from database") and commands (such as "Custom SQL statement") insert [[parameters]] as plain text into the generated SQL statement which can make them vulnerable to SQL injection. Don't use parameters in such actions when parameter values can't be trusted or sanitized.
  
  
  
connectors.txt · Last modified: 2024/04/19 00:37 by dmitry

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki