Secondary regions do not work with RBR tables (#19436)

rmloveland · web-flow · commit a084061bbc3c · 2025-03-18T18:16:03.000Z
Fixes DOC-8959 NB. This PR includes backported changes to v23.*, v24.*, and v25.*
diff --git a/src/current/_includes/v23.1/known-limitations/secondary-regions-with-regional-by-row-tables.md b/src/current/_includes/v23.1/known-limitations/secondary-regions-with-regional-by-row-tables.md
@@ -0,0 +1,3 @@
+[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
+
+Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.
diff --git a/src/current/_includes/v23.1/sql/regional-by-row-table-description.md b/src/current/_includes/v23.1/sql/regional-by-row-table-description.md
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
 
 For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
 
-For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
diff --git a/src/current/_includes/v23.2/known-limitations/secondary-regions-with-regional-by-row-tables.md b/src/current/_includes/v23.2/known-limitations/secondary-regions-with-regional-by-row-tables.md
@@ -0,0 +1,3 @@
+[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
+
+Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.
diff --git a/src/current/_includes/v23.2/sql/regional-by-row-table-description.md b/src/current/_includes/v23.2/sql/regional-by-row-table-description.md
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
 
 For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
 
-For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
diff --git a/src/current/_includes/v24.1/known-limitations/secondary-regions-with-regional-by-row-tables.md b/src/current/_includes/v24.1/known-limitations/secondary-regions-with-regional-by-row-tables.md
@@ -0,0 +1,3 @@
+[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
+
+Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.
diff --git a/src/current/_includes/v24.1/sql/regional-by-row-table-description.md b/src/current/_includes/v24.1/sql/regional-by-row-table-description.md
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
 
 For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
 
-For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
diff --git a/src/current/_includes/v24.2/known-limitations/secondary-regions-with-regional-by-row-tables.md b/src/current/_includes/v24.2/known-limitations/secondary-regions-with-regional-by-row-tables.md
@@ -0,0 +1,3 @@
+[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
+
+Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.
diff --git a/src/current/_includes/v24.2/sql/regional-by-row-table-description.md b/src/current/_includes/v24.2/sql/regional-by-row-table-description.md
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
 
 For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
 
-For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
diff --git a/src/current/_includes/v24.3/known-limitations/secondary-regions-with-regional-by-row-tables.md b/src/current/_includes/v24.3/known-limitations/secondary-regions-with-regional-by-row-tables.md
@@ -0,0 +1,3 @@
+[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
+
+Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.
diff --git a/src/current/_includes/v24.3/sql/regional-by-row-table-description.md b/src/current/_includes/v24.3/sql/regional-by-row-table-description.md
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
 
 For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
 
-For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
diff --git a/src/current/_includes/v25.1/known-limitations/secondary-regions-with-regional-by-row-tables.md b/src/current/_includes/v25.1/known-limitations/secondary-regions-with-regional-by-row-tables.md
@@ -0,0 +1,3 @@
+[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
+
+Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.
diff --git a/src/current/_includes/v25.1/sql/regional-by-row-table-description.md b/src/current/_includes/v25.1/sql/regional-by-row-table-description.md
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
 
 For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
 
-For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
+
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
diff --git a/src/current/v23.1/alter-database.md b/src/current/v23.1/alter-database.md
@@ -433,6 +433,8 @@ If the [primary region](#set-primary-region) fails, the secondary region becomes
 
 {{site.data.alerts.callout_danger}}
 In order to add a secondary region with `ALTER DATABASE ... SET SECONDARY REGION`, you must first set a primary database region with [`SET PRIMARY REGION`](#set-primary-region), or when [creating the database]({% link {{ page.version.version }}/create-database.md %}). For an example showing how to add a secondary region with `ALTER DATABASE`, see [Set the secondary region](#set-the-secondary-region).
+
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
 {{site.data.alerts.end}}
 
 For examples, see [Manage regions](#manage-regions).
@@ -550,6 +552,10 @@ ALTER DATABASE SET SECONDARY REGION
 
 Now, the `"us-west1"` region will act as the primary region if the original primary region fails.
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 #### Unset the secondary region
 
 To unset an existing [database region]({% link {{ page.version.version }}/multiregion-overview.md %}#database-regions) as the [secondary region]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) on a multi-region database, use the [`DROP SECONDARY REGION`](#drop-secondary-region) statement:
diff --git a/src/current/v23.1/create-database.md b/src/current/v23.1/create-database.md
@@ -188,6 +188,10 @@ CREATE DATABASE
 
 For more information about secondary regions, see [Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions).
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 ## See also
 
 - [`SHOW DATABASES`]({% link {{ page.version.version }}/show-databases.md %})
diff --git a/src/current/v23.1/known-limitations.md b/src/current/v23.1/known-limitations.md
@@ -702,6 +702,10 @@ If you think a rollback of a column-dropping schema change has occurred, check t
 
 {% include {{ page.version.version }}/known-limitations/drop-unique-index-from-create-table.md %}
 
+### Secondary regions and regional by row tables
+
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+
 ### Row-Level TTL limitations
 
 {% include {{page.version.version}}/known-limitations/row-level-ttl-limitations.md %}
diff --git a/src/current/v23.1/migrate-to-multiregion-sql.md b/src/current/v23.1/migrate-to-multiregion-sql.md
@@ -246,6 +246,10 @@ SHOW ZONE CONFIGURATION FROM TABLE users;
 
 ~~~
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 #### Global tables
 
 A [`GLOBAL`]({% link {{ page.version.version }}/table-localities.md %}) table differs from the default by setting the following zone configuration settings:
diff --git a/src/current/v23.1/multiregion-overview.md b/src/current/v23.1/multiregion-overview.md
@@ -131,6 +131,10 @@ If you are using [super regions](#super-regions) in your cluster, there are addi
 </ul>
 {{site.data.alerts.end}}
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 ## Survival goals
 
 A _survival goal_ dictates how many simultaneous failure(s) a database can survive. All tables within the same database operate with the **same survival goal**. Each database can have its own survival goal setting.
diff --git a/src/current/v23.2/alter-database.md b/src/current/v23.2/alter-database.md
@@ -433,6 +433,8 @@ If the [primary region](#set-primary-region) fails, the secondary region becomes
 
 {{site.data.alerts.callout_danger}}
 In order to add a secondary region with `ALTER DATABASE ... SET SECONDARY REGION`, you must first set a primary database region with [`SET PRIMARY REGION`](#set-primary-region), or when [creating the database]({% link {{ page.version.version }}/create-database.md %}). For an example showing how to add a secondary region with `ALTER DATABASE`, see [Set the secondary region](#set-the-secondary-region).
+
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
 {{site.data.alerts.end}}
 
 For examples, see [Manage regions](#manage-regions).
@@ -550,6 +552,10 @@ ALTER DATABASE SET SECONDARY REGION
 
 Now, the `"us-west1"` region will act as the primary region if the original primary region fails.
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 #### Unset the secondary region
 
 To unset an existing [database region]({% link {{ page.version.version }}/multiregion-overview.md %}#database-regions) as the [secondary region]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) on a multi-region database, use the [`DROP SECONDARY REGION`](#drop-secondary-region) statement:
diff --git a/src/current/v23.2/create-database.md b/src/current/v23.2/create-database.md
@@ -188,6 +188,10 @@ CREATE DATABASE
 
 For more information about secondary regions, see [Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions).
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 ## See also
 
 - [`SHOW DATABASES`]({% link {{ page.version.version }}/show-databases.md %})
diff --git a/src/current/v23.2/known-limitations.md b/src/current/v23.2/known-limitations.md
@@ -701,6 +701,10 @@ This is because the state flip is effected by the CLI program at the end. Only t
 
 {% include {{ page.version.version }}/known-limitations/drop-unique-index-from-create-table.md %}
 
+### Secondary regions and regional by row tables
+
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+
 ### Row-Level TTL limitations
 
 {% include {{page.version.version}}/known-limitations/row-level-ttl-limitations.md %}
diff --git a/src/current/v23.2/migrate-to-multiregion-sql.md b/src/current/v23.2/migrate-to-multiregion-sql.md
@@ -246,6 +246,10 @@ SHOW ZONE CONFIGURATION FROM TABLE users;
 
 ~~~
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 #### Global tables
 
 A [`GLOBAL`]({% link {{ page.version.version }}/table-localities.md %}) table differs from the default by setting the following zone configuration settings:
diff --git a/src/current/v23.2/multiregion-overview.md b/src/current/v23.2/multiregion-overview.md
@@ -135,6 +135,10 @@ If you are using [super regions](#super-regions) in your cluster, there are addi
 </ul>
 {{site.data.alerts.end}}
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 ## Survival goals
 
 A _survival goal_ dictates how many simultaneous failure(s) a database can survive. All tables within the same database operate with the **same survival goal**. Each database can have its own survival goal setting.
diff --git a/src/current/v24.1/alter-database.md b/src/current/v24.1/alter-database.md
@@ -437,6 +437,8 @@ If the [primary region](#set-primary-region) fails, the secondary region becomes
 
 {{site.data.alerts.callout_danger}}
 In order to add a secondary region with `ALTER DATABASE ... SET SECONDARY REGION`, you must first set a primary database region with [`SET PRIMARY REGION`](#set-primary-region), or when [creating the database]({% link {{ page.version.version }}/create-database.md %}). For an example showing how to add a secondary region with `ALTER DATABASE`, see [Set the secondary region](#set-the-secondary-region).
+
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
 {{site.data.alerts.end}}
 
 For examples, see [Manage regions](#manage-regions).
@@ -554,6 +556,10 @@ ALTER DATABASE SET SECONDARY REGION
 
 Now, the `"us-west1"` region will act as the primary region if the original primary region fails.
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 #### Unset the secondary region
 
 To unset an existing [database region]({% link {{ page.version.version }}/multiregion-overview.md %}#database-regions) as the [secondary region]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) on a multi-region database, use the [`DROP SECONDARY REGION`](#drop-secondary-region) statement:
diff --git a/src/current/v24.1/create-database.md b/src/current/v24.1/create-database.md
@@ -188,6 +188,10 @@ CREATE DATABASE
 
 For more information about secondary regions, see [Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions).
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 ## See also
 
 - [`SHOW DATABASES`]({% link {{ page.version.version }}/show-databases.md %})
diff --git a/src/current/v24.1/known-limitations.md b/src/current/v24.1/known-limitations.md
@@ -317,6 +317,10 @@ CockroachDB does not allow inverted indexes with a [`STORING` column]({% link {{
 
 {% include {{ page.version.version }}/known-limitations/expression-index-limitations.md %}
 
+#### Secondary regions and regional by row tables
+
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+
 ### Data types
 
 #### Spatial support limitations
diff --git a/src/current/v24.1/migrate-to-multiregion-sql.md b/src/current/v24.1/migrate-to-multiregion-sql.md
@@ -246,6 +246,10 @@ SHOW ZONE CONFIGURATION FROM TABLE users;
 
 ~~~
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 #### Global tables
 
 A [`GLOBAL`]({% link {{ page.version.version }}/table-localities.md %}) table differs from the default by setting the following zone configuration settings:
diff --git a/src/current/v24.1/multiregion-overview.md b/src/current/v24.1/multiregion-overview.md
@@ -135,6 +135,10 @@ If you are using [super regions](#super-regions) in your cluster, there are addi
 </ul>
 {{site.data.alerts.end}}
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 ## Survival goals
 
 A _survival goal_ dictates how many simultaneous failure(s) a database can survive. All tables within the same database operate with the **same survival goal**. Each database can have its own survival goal setting.
diff --git a/src/current/v24.2/alter-database.md b/src/current/v24.2/alter-database.md
@@ -437,6 +437,8 @@ If the [primary region](#set-primary-region) fails, the secondary region becomes
 
 {{site.data.alerts.callout_danger}}
 In order to add a secondary region with `ALTER DATABASE ... SET SECONDARY REGION`, you must first set a primary database region with [`SET PRIMARY REGION`](#set-primary-region), or when [creating the database]({% link {{ page.version.version }}/create-database.md %}). For an example showing how to add a secondary region with `ALTER DATABASE`, see [Set the secondary region](#set-the-secondary-region).
+
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
 {{site.data.alerts.end}}
 
 For examples, see [Manage regions](#manage-regions).
@@ -554,6 +556,10 @@ ALTER DATABASE SET SECONDARY REGION
 
 Now, the `"us-west1"` region will act as the primary region if the original primary region fails.
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 #### Unset the secondary region
 
 To unset an existing [database region]({% link {{ page.version.version }}/multiregion-overview.md %}#database-regions) as the [secondary region]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) on a multi-region database, use the [`DROP SECONDARY REGION`](#drop-secondary-region) statement:
diff --git a/src/current/v24.2/create-database.md b/src/current/v24.2/create-database.md
@@ -188,6 +188,10 @@ CREATE DATABASE
 
 For more information about secondary regions, see [Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions).
 
+{{site.data.alerts.callout_danger}}
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+{{site.data.alerts.end}}
+
 ## See also
 
 - [`SHOW DATABASES`]({% link {{ page.version.version }}/show-databases.md %})
diff --git a/src/current/v24.2/known-limitations.md b/src/current/v24.2/known-limitations.md
@@ -298,6 +298,10 @@ CockroachDB does not allow inverted indexes with a [`STORING` column]({% link {{
 
 {% include {{ page.version.version }}/known-limitations/expression-index-limitations.md %}
 
+#### Secondary regions and regional by row tables
+
+{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
+
 ### Data types
 
 #### Spatial support limitations
diff --git a/src/current/v24.2/migrate-to-multiregion-sql.md b/src/current/v24.2/migrate-to-multiregion-sql.md
diff --git a/src/current/v24.2/multiregion-overview.md b/src/current/v24.2/multiregion-overview.md
diff --git a/src/current/v24.3/alter-database.md b/src/current/v24.3/alter-database.md
diff --git a/src/current/v24.3/create-database.md b/src/current/v24.3/create-database.md
diff --git a/src/current/v24.3/known-limitations.md b/src/current/v24.3/known-limitations.md
diff --git a/src/current/v24.3/migrate-to-multiregion-sql.md b/src/current/v24.3/migrate-to-multiregion-sql.md
diff --git a/src/current/v24.3/multiregion-overview.md b/src/current/v24.3/multiregion-overview.md
diff --git a/src/current/v25.1/alter-database.md b/src/current/v25.1/alter-database.md
diff --git a/src/current/v25.1/create-database.md b/src/current/v25.1/create-database.md
diff --git a/src/current/v25.1/known-limitations.md b/src/current/v25.1/known-limitations.md
diff --git a/src/current/v25.1/migrate-to-multiregion-sql.md b/src/current/v25.1/migrate-to-multiregion-sql.md
diff --git a/src/current/v25.1/multiregion-overview.md b/src/current/v25.1/multiregion-overview.md
diff --git a/src/current/v25.1/table-localities.md b/src/current/v25.1/table-localities.md

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,3 @@`
	`1`	+[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
	`2`	`+`
	`3`	`+Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.`