Differences

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

--- connectors [2020/11/25 18:52] – [Connectors] dmitry
+++ connectors [2020/11/28 07:28] – [Database connectors] dmitry
@@ Line 17: / Line 17: @@
 === Server-hosted connector repository ===
-A shared repository can be served to Desktop users from EasyMorph Server. This provides better security as the repository files can't be accessed by Desktop users. Additionally, connectors can be protected from copying and thus embedding. Finally, if a repository is provided from a Server space with Active Directory authentication model, then only the users that are whitelisted in the space settings can access and use the repository.
+A shared repository can be served to Desktop users from EasyMorph Server. This ensures stronger security:
+  * The repository files are not exposed to users
+  * Connectors can be protected from copying and thus embedding
+  * If a repository is provided from a Server space with the Active Directory authentication mode, then only the users that are whitelisted in the space settings can access and use the repository
+  * EasyMorph Server allows locking and encrypting repositories
+  * User tasks (projects) on EasyMorph Server can be forced to run under Windows accounts that don't have access to the system folder that holds repositories.
 In order to use a Server-hosted repository, the Server Link must be configured in Desktop. For more details please read the "EasyMorph Server Administrator Guide" which comes with the Server installer.
 ==== Database connectors ====
-Currently EasyMorph supports these database types:
+Currently EasyMorph supports these database types and SQL dialects:
-  * MS SQL Server
+^ Database type   ^ Driver type ^ Notes ^
-  * MySQL
+|SQL Server / Azure SQL Database	   |ODBC / Native  |Bulk export supported (only for the native driver) |
-  * Oracle Database
+|Oracle	           |ODBC / Native  | |
-  * PostgreSQL
+|MySQL	           |ODBC / Native  | |
-  * SQLite
+|PostgreSQL	   |ODBC / Native  |Bulk export supported (only for the native driver) |
-  * Amazon Redshift
+|SQLite	           |ODBC / Native  | |
-  * DB2
+|Amazon Redshift   |ODBC / Native  | |
-  * Vertica
+|Snowflake         |ODBC / Native  |Bulk export supported (only for the ODBC driver) |
-  * SAP HANA
+|DB2               |ODBC only  | |
-  * Apache Hive
+|DB2 for iSeries (AS/400) |ODBC only  | |
-  * Generic ODBC (custom SQL only)
+|Vertica           |ODBC only  | |
+|SAP HANA          |ODBC only  | |
+|Apache Hive       |ODBC only  |Only import via visual queries, and custom SQL |
+|Google BigQuery   |ODBC only  |Only import via visual queries, and custom SQL |
+|Generic SQL:2003  |ODBC only  |Custom SQL only |
+Database ODBC connection are configured in EasyMorph by creating an ODBC connector, selecting a 64-bit ODBC DSN configured in Windows, and then specifying the required SQL dialect (if it wasn't auto-detected) in the connector settings.
 ==== Email connectors ====
@@ Line 64: / Line 75: @@
 While EasyMorph encrypts connection passwords stored in projects and repositories, this can't be considered a strong security measure. Therefore for addition security consider the following:
-  * Make sure that the database account used in connector is read-only and doesn't expose unnecessary objects (e.g. schemas, tables, etc.)
+  * Use Server-hosted connector repositories when possible, otherwise limit access to shared repositories using standard Windows file system permissions
-  * Limit access to shared repositories using standard Windows file system permissions
+  * For Server repositories consider using the option for locking and encrypting repository; the option is described in the "EasyMorph Server Administrator Guide" that comes with the Server installer
-  * When using embedded connectors make sure there is full control over distribution of a project with embedded connectors
+  * In connectors, use accounts that are read-only and doesn't expose unnecessary objects (e.g. schemas, tables, etc.)
-  * Don't use embedded connectors for very sensitive information
+  * 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 custom SQL queries using connectors
+  * Keep in mind that users may write custom SQL queries/statements using connectors