Merge pull request #4763 from EnterpriseDB/docs/migration_toolkit/55-…

…6-1-release

Migration Toolkit: v55.6.1 release

product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx

@@ -393,6 +393,8 @@ The following options control the way MTK migrates data in parallel.
 
 Use the `-loaderCount` option to specify the number of parallel threads available in the pool to perform data load in parallel. This option is particularly useful if the host system that's running Migration Toolkit has high-end CPU and RAM resources. While `value` can be any nonzero, positive number, we recommend that value not exceed the number of CPU cores. For example, a dual-core CPU has an optimal value of `2`. The default is `1`.
 
+The number of table-level threads can introduce overhead on the source database server depending on the table size and certain memory configurations, like `shared_buffers` and `work_mem` (memory configuration should be set to optimal values for the database server). It is recommended that for very large tables you try the lower `-loaderCount` option value, according to the total cores available on the machine, to calculate the optimal `-loaderCount` value.
+
 !!! Note
     When multiple threads are used, depending on the actual number of threads and table data size, you might need to adjust the memory heap size for the Migration Toolkit.
 

product_docs/docs/migration_toolkit/55/mtk_rel_notes/index.mdx

@@ -3,6 +3,7 @@ title: "Release notes"
 redirects:
   - ../01_whats_new/
 navigation:
+ - mtk_5561_rel_notes
  - mtk_556_rel_notes
  - mtk_555_rel_notes
  - mtk_554_rel_notes
@@ -19,6 +20,7 @@ The Migration Toolkit documentation describes the latest version of Migration To
 
 | Version | Release Date | 
 | ------- | ------------ | 
+| [55.6.1](mtk_5561_rel_notes) | 06 Sep 2023  |
 | [55.6.0](mtk_556_rel_notes) | 25 May 2023  |
 | [55.5.0](mtk_555_rel_notes) | 14 Feb 2023  |
 | [55.4.0](mtk_554_rel_notes) | 29 Nov 2022  |

product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_5561_rel_notes.mdx

@@ -0,0 +1,16 @@
+---
+title: "Version 55.6.1"
+---
+
+Released: 06 Sep 2023
+
+New features, enhancements, bug fixes, and other changes in Migration Toolkit 55.6.1 include:
+
+|     Type     |                                                                                                                                                                                         Description                                                                                                                                                                                         |
+| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Enhancement  | Updated the table-level parallel loading capability with to reduce the overhead on the source database by using range-based criterion for loading each individual table data chunk instead of a fetch-offset approach. This optimization is applicable when the table primary key/unique constraint is based on a non-composite numeric type attribute. [Support ticket #93360] |
+| Bug fix | Fixed the issue where a data copy fails when migrating a source Oracle table that has a full-width character in its name. [Support ticket #93552] |
+| Bug fix | Fixed an issue that caused a data copy to fail when a source MySQL table name contains a dash character. [Support ticket #95794] |
+| Bug fix | Fixed an issue that resulted in table creation failure for a source MySQL table that has a `DEFAULT` clause defined with one or more single-quote characters. [Support ticket #95794]|
+| Bug fix | Fixed an issue that caused a data copy to fail when a source MySQL table uses a MySQL reserved word as its name. [Support ticket #94822] |
+| Bug fix | Fixed the issue encountered during Microsoft SQL Server to EDB Postgres Advanced Server, Oracle to EDB Postgres Advanced Server, or EDB Postgres Advanced Server to Oracle `-dataOnly` migrations where foreign key constraints are not restored after the data copy completes if the `-tables` option is specified and the parent table isn't included in the list of specified tables. |