0005344: Documentation for Bulk Loading

symmetric-assemble/src/asciidoc/appendix/databases.ad

@@ -31,8 +31,8 @@ by database.
 |
 |
 |
-|?
-|?
+|
+|
 
 |DB2
 |9.5
@@ -44,8 +44,8 @@ by database.
 |✔
 |✔
 |✔
-|?
-|?
+|
+|
 
 |DB2
 |10,11
@@ -57,8 +57,8 @@ by database.
 |✔
 |✔ 
 |✔
-|?
-|?
+|
+|
 
 |DB2 for IBM i *
 |6
@@ -70,8 +70,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|
+|
 
 |DB2 for IBM z/OS *
 |10
@@ -83,8 +83,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|
+|
 
 |Derby
 |10.3.2.1
@@ -96,8 +96,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|
+|
 
 |Elasticsearch *
 |7.13.2
@@ -109,8 +109,8 @@ by database.
 |
 |
 |
-|?
-|?
+|
+|
 
 |Firebird
 |2.0
@@ -135,8 +135,8 @@ by database.
 |
 |
 |
-|?
-|?
+|
+|
 
 |H2
 |1.x
@@ -148,8 +148,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|
+|
 
 |HSQLDB
 |1.8
@@ -161,8 +161,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|
+|
 
 |HSQLDB
 |2.0
@@ -174,8 +174,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|
+|
 
 |Informix
 |11
@@ -187,8 +187,8 @@ by database.
 |
 |
 |
-|?
-|?
+|
+|
 
 |Ingres
 |11 and above
@@ -200,8 +200,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|
+|
 
 |Interbase
 |9.0
@@ -213,8 +213,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|
+|
 
 |MySQL
 |5.0.2 and above
@@ -226,8 +226,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|✔
+|✔
 
 |MariaDB
 |5.1 and above
@@ -239,8 +239,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|✔
+|✔
 
 |NuoDB
 |2.6 and above
@@ -252,8 +252,8 @@ by database.
 |
 |✔
 |
-|?
-|?
+|
+|
 
 |Oracle
 |10g and above
@@ -291,8 +291,8 @@ by database.
 |
 |
 |
-|?
-|?
+|
+|
 
 |Snowflake *
 |6.13 and above
@@ -318,8 +318,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|
+|
 
 |SQL Anywhere
 |9
@@ -331,8 +331,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|
+|
 
 |SQL Server
 |2005 and above
@@ -357,8 +357,8 @@ by database.
 |✔
 |
 |
-|?
-|?
+|
+|
 
 |SQLite
 |3.x
@@ -396,8 +396,8 @@ by database.
 |
 |
 |
-|?
-|?
+|
+|
 
 |Tibero
 |6 and above
@@ -409,8 +409,8 @@ by database.
 |✔
 |✔
 |
-|?
-|?
+|
+|
 
 |===
 

symmetric-assemble/src/asciidoc/appendix/elasticsearch.ad

@@ -16,7 +16,7 @@ Setup the Elasticsearch node by using the <<Add Node,Connect Database>> wizard a
 image::images/appendix/elasticsearch-node-setup.png[]
 
 
-==== Loading Data
+==== Bulk Loading
 
 
 ===== Setup reload channels for bulk loading.

symmetric-assemble/src/asciidoc/appendix/firebird.ad

@@ -53,6 +53,6 @@ Firebird 3 is supported, however legacy authentication must be enabled in order
 | Blob | No
 |===
 
-==== Loading Data
+==== Bulk Loading
 
 SymmetricDS has bulk loading capability available for Firebird, when registering a Firebird database with SymmetricDS, bulk loading will be checked by default. SymmetricDS specifies data loader types on a channel by channel basis. Once you have your database registered, to utilize bulk loading versus straight JDBC insert, specify the Bulk Loader ("bulk") in the data_loader_type column of sym_channel table.

symmetric-assemble/src/asciidoc/appendix/mariadb.ad

@@ -24,7 +24,7 @@ See MySQL notes.  You can use either the MySQL or MariaDB driver for this dialec
 |Point, LineString, Polygon, MultiPoint, MultiLinestring, MultiPolygon, GeometryCollection, Geometry| No
 |===
 
-==== Loading Data
+==== Bulk Loading
 When registering a Maria database with SymmetricDS, bulk loading will be checked by default.
 
 image::images/appendix/mysql-enable-bulk-loading.png[]

symmetric-assemble/src/asciidoc/appendix/mssqlserver.ad

@@ -19,7 +19,7 @@ If SQL Server is configured with a default collation that does NOT support unico
 a table has character based primary keys.  This is because statements are prepared for a unicode type and as a result the indexes are not used.  You can turn this 
 functionality off in JTDS by appending the following to your db.url:  ;sendStringParametersAsUnicode=false
 
-==== SQL Server Permissions
+==== Permissions
 
 SymmetricDS can be configured to work with a variety SQL Server configurations.  It is possible to install SymmetricDS in the same database and schema with the same user account your application runs.   
 However you can also set it up to run in its own database with a designated user.   Whichever configuration you choose below are the permissions required for SymmetricDS to run.
@@ -122,6 +122,6 @@ endif::pro[]
 |Spatial Data Types|No
 |===
 
-==== Loading Data
+==== Bulk Loading
 
 When registering a SQL Server database with SymmetricDS, bulk loading will be be checked by default. In order to make use of bulk loading, the user must provide a path to a bcp executable (installation for this executable is linked in the Connect Database Wizard when asked about bulk loading).

symmetric-assemble/src/asciidoc/appendix/mysql.ad

@@ -97,7 +97,7 @@ endif::pro[]
 |Geometry, Point, LineString, Polygon, GeometryCollection, MultiPoint, MultiLinestring, MultiPolygon|No
 |===
 
-==== Loading Data
+==== Bulk Loading
 When registering a MySQL database with SymmetricDS, bulk loading will be checked by default.
 
 image::images/appendix/mysql-enable-bulk-loading.png[]

symmetric-assemble/src/asciidoc/appendix/opensearch.ad

@@ -20,7 +20,7 @@ After hitting next you can setup advanced options for your OpenSearch node.
 image::images/appendix/opensearch-advanced-settings.png[]
 
 
-==== Loading Data
+==== Bulk Loading
 
 
 ===== Setup reload channels for bulk loading.

symmetric-assemble/src/asciidoc/appendix/oracle.ad

@@ -2,7 +2,7 @@
 === Oracle
 This section describes Oracle specific SymmetricDS details.
 
-==== Database Permissions
+==== Permissions
 The SymmetricDS database user generally needs privileges for connecting and creating tables (including indexes), triggers, sequences, 
 and procedures (including packages and functions). For change data capture, use the following permissions:
 
@@ -50,7 +50,7 @@ then set `use_capture_lobs` to 1 in the <<TRIGGER>> table and `contains_big_lobs
 sym_data is cast to a clob which prevents truncation at 4k.  There is overhead for both of these settings
 * When multiple triggers are defined on the same table, then the order in which the triggers occur appears to be arbitrary
 
-==== Loading Data
+==== Bulk Loading
 SymmetricDS has bulk loading capability available for Oracle. SymmetricDS specifies data loader types on a channel by channel basis. 
 
 To utilize bulk loading with Oracle, you should create a user that is not the default system user of the database. Whatever user you end up using, make sure it also has the permissions mentioned above in the Database Permission section, as well as the ones mentioned below. It's important to note that SQL Loader (what Oracle uses to bulk load) will not work if either your user name or password contains a '@' symbol, so make sure to avoid this in both your username and password.

symmetric-assemble/src/asciidoc/appendix/postgresql.ad

@@ -37,7 +37,7 @@ If you want SymmetricDS to install into a schema other than public you can alter
 alter user {user name} set search_path to {schema name};
 ----
 
-==== Postgres Permissions
+==== Permissions
 
 If SymmetricDS is connected into a different schema than the application tables and a different user account is used to write to the the application tables the following permissions need to be granted to the application user to access the SymmetricDS schema
 
@@ -84,7 +84,7 @@ endif::pro[]
 |Point, Lseg, Box, Path, Polygon, Circle|Yes
 |===
 
-==== Loading Data
+==== Bulk Loading
 
 SymmetricDS has bulk loading capability available for Postgres, when registering a PostgreSQL database with SymmetricDS, bulk loading will be checked by default. SymmetricDS specifies data loader types on a channel by channel basis.
 To utilize Postgres Bulk loading versus straight JDBC insert, specify the Postgres Bulk Loader ("postgres_bulk") in the data_loader_type column of sym_channel.