From fefc56e75057bff638c056a9a2bc59901bbb48b0 Mon Sep 17 00:00:00 2001 From: Brandon Sanchez Date: Thu, 16 Oct 2025 16:28:16 -0400 Subject: [PATCH 1/4] Clarify that MOLT Fetch does not migrate sequences --- .../_includes/molt/migration-schema-design-practices.md | 4 ++++ src/current/molt/molt-fetch.md | 2 ++ 2 files changed, 6 insertions(+) diff --git a/src/current/_includes/molt/migration-schema-design-practices.md b/src/current/_includes/molt/migration-schema-design-practices.md index 5cc0828b1bf..ce260791275 100644 --- a/src/current/_includes/molt/migration-schema-design-practices.md +++ b/src/current/_includes/molt/migration-schema-design-practices.md @@ -32,6 +32,10 @@ Convert the source schema into a CockroachDB-compatible schema. CockroachDB supp - Every table **must** have an explicit primary key. For more information, refer to [Primary key best practices]({% link {{ site.current_cloud_version }}/schema-design-table.md %}#primary-key-best-practices). +{{site.data.alerts.callout_danger}} +Avoid using sequential keys. To learn more about the performance issues that can result from their use, please read [our advice on indexing with sequential keys]({% link {{site.current_cloud_version}}/sql-faqs.md %}#how-do-i-generate-unique-slowly-increasing-sequential-numbers-in-cockroachdb). If a sequential key is necessary in your CockroachDB table, you will need to create it manually, after using [MOLT Fetch]({% link molt/molt-fetch.md %}). +{{site.data.alerts.end}} + - Review [Transformations]({% link molt/molt-fetch.md %}#transformations) to understand how computed columns and partitioned tables can be mapped to the target, and how target tables can be renamed. - By default on CockroachDB, `INT` is an alias for `INT8`, which creates 64-bit signed integers. PostgreSQL and MySQL default to 32-bit integers. Depending on your source database or application requirements, you may need to change the integer size to `4`. For more information, refer to [Considerations for 64-bit signed integers]({% link {{ site.current_cloud_version }}/int.md %}#considerations-for-64-bit-signed-integers). \ No newline at end of file diff --git a/src/current/molt/molt-fetch.md b/src/current/molt/molt-fetch.md index e52b2bc8ed7..f6a6e54a0ae 100644 --- a/src/current/molt/molt-fetch.md +++ b/src/current/molt/molt-fetch.md @@ -125,6 +125,8 @@ To verify that your connections and configuration work properly, run MOLT Fetch - {% include molt/molt-drop-constraints-indexes.md %} +- MOLT Fetch does not support migrating sequences. If your source database contains sequences, please read [our advice on indexing with sequential keys]({% link {{site.current_cloud_version}}/sql-faqs.md %}#how-do-i-generate-unique-slowly-increasing-sequential-numbers-in-cockroachdb). If a sequential key is necessary in your CockroachDB table, you will need to create it manually, after using MOLT Fetch. + ## Security recommendations Cockroach Labs **strongly** recommends the following: From c6bd5a58a8bb09ecce5cbd991ffe26ba4b369959 Mon Sep 17 00:00:00 2001 From: Brandon Sanchez Date: Mon, 20 Oct 2025 15:23:03 -0400 Subject: [PATCH 2/4] made changes based on Tuan's feedback --- src/current/_includes/molt/migration-schema-design-practices.md | 2 +- src/current/molt/molt-fetch.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/current/_includes/molt/migration-schema-design-practices.md b/src/current/_includes/molt/migration-schema-design-practices.md index ce260791275..745f5d98100 100644 --- a/src/current/_includes/molt/migration-schema-design-practices.md +++ b/src/current/_includes/molt/migration-schema-design-practices.md @@ -33,7 +33,7 @@ Convert the source schema into a CockroachDB-compatible schema. CockroachDB supp - Every table **must** have an explicit primary key. For more information, refer to [Primary key best practices]({% link {{ site.current_cloud_version }}/schema-design-table.md %}#primary-key-best-practices). {{site.data.alerts.callout_danger}} -Avoid using sequential keys. To learn more about the performance issues that can result from their use, please read [our advice on indexing with sequential keys]({% link {{site.current_cloud_version}}/sql-faqs.md %}#how-do-i-generate-unique-slowly-increasing-sequential-numbers-in-cockroachdb). If a sequential key is necessary in your CockroachDB table, you will need to create it manually, after using [MOLT Fetch]({% link molt/molt-fetch.md %}). +Avoid using sequential keys. To learn more about the performance issues that can result from their use, read [our advice on indexing with sequential keys]({% link {{site.current_cloud_version}}/sql-faqs.md %}#how-do-i-generate-unique-slowly-increasing-sequential-numbers-in-cockroachdb). If a sequential key is necessary in your CockroachDB table, you will need to create it manually, after using [MOLT Fetch]({% link molt/molt-fetch.md %}). {{site.data.alerts.end}} - Review [Transformations]({% link molt/molt-fetch.md %}#transformations) to understand how computed columns and partitioned tables can be mapped to the target, and how target tables can be renamed. diff --git a/src/current/molt/molt-fetch.md b/src/current/molt/molt-fetch.md index f6a6e54a0ae..05a6dd3b698 100644 --- a/src/current/molt/molt-fetch.md +++ b/src/current/molt/molt-fetch.md @@ -125,7 +125,7 @@ To verify that your connections and configuration work properly, run MOLT Fetch - {% include molt/molt-drop-constraints-indexes.md %} -- MOLT Fetch does not support migrating sequences. If your source database contains sequences, please read [our advice on indexing with sequential keys]({% link {{site.current_cloud_version}}/sql-faqs.md %}#how-do-i-generate-unique-slowly-increasing-sequential-numbers-in-cockroachdb). If a sequential key is necessary in your CockroachDB table, you will need to create it manually, after using MOLT Fetch. +- MOLT Fetch does not support migrating sequences. If your source database contains sequences, read [our advice on indexing with sequential keys]({% link {{site.current_cloud_version}}/sql-faqs.md %}#how-do-i-generate-unique-slowly-increasing-sequential-numbers-in-cockroachdb). If a sequential key is necessary in your CockroachDB table, you will need to create it manually. After using MOLT Fetch to load and replicate the data onto the target, but before cutover, make sure to update each sequence's current value using [`setval()`]({% link {{site.current_cloud_version}}/functions-and-operators.md %}#sequence-functions) so that new inserts continue from the correct point. ## Security recommendations From 5c49c7d2a1f88b6c0b0438e1b5171cecb6348e17 Mon Sep 17 00:00:00 2001 From: Brandon Sanchez Date: Tue, 21 Oct 2025 16:47:37 -0400 Subject: [PATCH 3/4] made changes based on Ryan's feedback --- .../_includes/molt/migration-schema-design-practices.md | 6 +++--- src/current/molt/molt-fetch.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/current/_includes/molt/migration-schema-design-practices.md b/src/current/_includes/molt/migration-schema-design-practices.md index 745f5d98100..be799393f6f 100644 --- a/src/current/_includes/molt/migration-schema-design-practices.md +++ b/src/current/_includes/molt/migration-schema-design-practices.md @@ -32,9 +32,9 @@ Convert the source schema into a CockroachDB-compatible schema. CockroachDB supp - Every table **must** have an explicit primary key. For more information, refer to [Primary key best practices]({% link {{ site.current_cloud_version }}/schema-design-table.md %}#primary-key-best-practices). -{{site.data.alerts.callout_danger}} -Avoid using sequential keys. To learn more about the performance issues that can result from their use, read [our advice on indexing with sequential keys]({% link {{site.current_cloud_version}}/sql-faqs.md %}#how-do-i-generate-unique-slowly-increasing-sequential-numbers-in-cockroachdb). If a sequential key is necessary in your CockroachDB table, you will need to create it manually, after using [MOLT Fetch]({% link molt/molt-fetch.md %}). -{{site.data.alerts.end}} + {{site.data.alerts.callout_danger}} + Avoid using sequential keys. To learn more about the performance issues that can result from their use, refer to the [guidance on indexing with sequential keys]({% link {{site.current_cloud_version}}/sql-faqs.md %}#how-do-i-generate-unique-slowly-increasing-sequential-numbers-in-cockroachdb). If a sequential key is necessary in your CockroachDB table, you must create it manually, after using [MOLT Fetch]({% link molt/molt-fetch.md %}) to load and replicate the data. + {{site.data.alerts.end}} - Review [Transformations]({% link molt/molt-fetch.md %}#transformations) to understand how computed columns and partitioned tables can be mapped to the target, and how target tables can be renamed. diff --git a/src/current/molt/molt-fetch.md b/src/current/molt/molt-fetch.md index 05a6dd3b698..04a44e8e1d5 100644 --- a/src/current/molt/molt-fetch.md +++ b/src/current/molt/molt-fetch.md @@ -125,7 +125,7 @@ To verify that your connections and configuration work properly, run MOLT Fetch - {% include molt/molt-drop-constraints-indexes.md %} -- MOLT Fetch does not support migrating sequences. If your source database contains sequences, read [our advice on indexing with sequential keys]({% link {{site.current_cloud_version}}/sql-faqs.md %}#how-do-i-generate-unique-slowly-increasing-sequential-numbers-in-cockroachdb). If a sequential key is necessary in your CockroachDB table, you will need to create it manually. After using MOLT Fetch to load and replicate the data onto the target, but before cutover, make sure to update each sequence's current value using [`setval()`]({% link {{site.current_cloud_version}}/functions-and-operators.md %}#sequence-functions) so that new inserts continue from the correct point. +- MOLT Fetch does not support migrating sequences. If your source database contains sequences, refer to the [guidance on indexing with sequential keys]({% link {{site.current_cloud_version}}/sql-faqs.md %}#how-do-i-generate-unique-slowly-increasing-sequential-numbers-in-cockroachdb). If a sequential key is necessary in your CockroachDB table, you must create it manually. After using MOLT Fetch to load and replicate the data onto the target, but before cutover, make sure to update each sequence's current value using [`setval()`]({% link {{site.current_cloud_version}}/functions-and-operators.md %}#sequence-functions) so that new inserts continue from the correct point. ## Security recommendations From 517462d5962e16c8dd446453d7ea3bacd42fa2ba Mon Sep 17 00:00:00 2001 From: Brandon Sanchez Date: Tue, 21 Oct 2025 17:04:28 -0400 Subject: [PATCH 4/4] empty commit to retrigger build