20260427 doc 16275 page deletion batch 6

src/current/_data/redirects.yml

@@ -1161,3 +1161,15 @@
 
 - destination: cockroachcloud/byoc-azure-deployment.md
   sources: ['cockroachcloud/byoc-deployment.md']
+
+- destination: multiregion-overview.md
+  sources: ['demo-low-latency-multi-region-deployment.md', 'migrate-to-multiregion-sql.md']
+  versions: ['v26.1', 'v26.2']
+
+- destination: performance-best-practices-overview.md
+  sources: ['performance.md', 'performance-benchmarking-with-tpcc-local.md', 'performance-benchmarking-with-tpcc-small.md', 'performance-benchmarking-with-tpcc-medium.md', 'performance-benchmarking-with-tpcc-large.md', 'performance-benchmarking-with-tpcc-local-multiregion.md']
+  versions: ['v26.1', 'v26.2']
+
+- destination: support-resources.md
+  sources: ['file-an-issue.md']
+  versions: ['v26.1', 'v26.2']

src/current/_includes/v26.1/misc/explore-benefits-see-also.md

@@ -1,4 +1,3 @@
 - [Replication & Rebalancing]({% link {{ page.version.version }}/demo-replication-and-rebalancing.md %})
 - [CockroachDB Resilience]({% link {{ page.version.version }}/demo-cockroachdb-resilience.md %})
-- [Low Latency Multi-Region Deployment]({% link {{ page.version.version }}/demo-low-latency-multi-region-deployment.md %})
 - [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})

src/current/_includes/v26.1/prod-deployment/insecure-test-load-balancing.md

@@ -4,10 +4,6 @@ CockroachDB comes with a number of [built-in workloads]({% link {{ page.version.
 Be sure that you have configured your network to allow traffic from the application to the load balancer. In this case, you will run the sample workload on one of your machines. The traffic source should therefore be the **internal (private)** IP address of that machine.
 {{site.data.alerts.end}}
 
-{{site.data.alerts.callout_success}}
-For comprehensive guidance on benchmarking CockroachDB with TPC-C, see [Performance Benchmarking]({% link {{ page.version.version }}/performance-benchmarking-with-tpcc-local.md %}).
-{{site.data.alerts.end}}
-
 1. SSH to the machine where you want the run the sample TPC-C workload.
 
     This should be a machine that is not running a CockroachDB node.

src/current/_includes/v26.1/prod-deployment/prod-see-also.md

@@ -2,6 +2,5 @@
 - [Manual Deployment]({% link {{ page.version.version }}/manual-deployment.md %})
 - [Orchestrated Deployment]({% link {{ page.version.version }}/kubernetes-overview.md %})
 - [Monitoring and Alerting]({% link {{ page.version.version }}/monitoring-and-alerting.md %})
-- [Performance Benchmarking]({% link {{ page.version.version }}/performance-benchmarking-with-tpcc-small.md %})
 - [Performance Tuning]({% link {{ page.version.version }}/performance-best-practices-overview.md %})
 - [Local Deployment]({% link {{ page.version.version }}/start-a-local-cluster.md %})

src/current/_includes/v26.1/prod-deployment/secure-test-load-balancing.md

@@ -4,8 +4,6 @@ CockroachDB comes with a number of [built-in workloads]({% link {{ page.version.
 Be sure that you have configured your network to allow traffic from the application to the load balancer. In this case, you will run the sample workload on one of your machines. The traffic source should therefore be the **internal (private)** IP address of that machine.
 {{site.data.alerts.end}}
 
-For comprehensive guidance on benchmarking CockroachDB with TPC-C, refer to [Performance Benchmarking]({% link {{ page.version.version }}/performance-benchmarking-with-tpcc-local.md %}).
-
 1. SSH to the machine where you want to run the sample TPC-C workload.
 
     This should be a machine that is not running a CockroachDB node, and it should already have a `certs` directory containing `ca.crt`, `client.root.crt`, and `client.root.key` files.

src/current/_includes/v26.1/sidebar-data/multi-region-capabilities.json

@@ -28,6 +28,12 @@
                 "urls": [
                 "/${VERSION}/partitioning.html"
                 ]
+            },
+            {
+                "title": "Data Domiciling with CockroachDB Tutorial",
+                "urls": [
+                "/${VERSION}/data-domiciling.html"
+                ]
             }
             ]
         },
@@ -42,29 +48,6 @@
             "urls": [
             "/${VERSION}/zone-config-extensions.html"
             ]
-        },
-        {
-            "title": "Multi-Region Tutorials",
-            "items": [
-                {
-                    "title": "Low Latency Reads and Writes",
-                    "urls": [
-                    "/${VERSION}/demo-low-latency-multi-region-deployment.html"
-                    ]
-                },
-                {
-                    "title": "Data Domiciling with CockroachDB",
-                    "urls": [
-                    "/${VERSION}/data-domiciling.html"
-                    ]
-                },
-                {
-                    "title": "Migrate to Multi-Region SQL with Replication Zones",
-                    "urls": [
-                    "/${VERSION}/migrate-to-multiregion-sql.html"
-                    ]
-                }
-            ]
         }
     ]
 }

src/current/_includes/v26.1/sidebar-data/reads-and-writes.json

@@ -113,13 +113,6 @@
         "/${VERSION}/local-testing.html"
       ]
     },
-    {
-      "title": "SQL Playground",
-      "is_top_level": true,
-      "urls": [
-        "https://www.cockroachlabs.com/docs/tutorials/sql-playground"
-      ]
-    },
     {
       "title": "Database Management Tools",
       "items": [

src/current/_includes/v26.1/sidebar-data/troubleshooting.json

@@ -74,39 +74,12 @@
           "/${VERSION}/troubleshoot-replication-zones.html"
         ]
       },
-      {
-        "title": "Benchmarking",
-        "items": [
-          {
-            "title": "Overview",
-            "urls": [
-              "/${VERSION}/performance.html"
-            ]
-          },
-          {
-            "title": "Benchmarking with TPC-C",
-            "urls": [
-              "/${VERSION}/performance-benchmarking-with-tpcc-local.html",
-              "/${VERSION}/performance-benchmarking-with-tpcc-local-multiregion.html",
-              "/${VERSION}/performance-benchmarking-with-tpcc-small.html",
-              "/${VERSION}/performance-benchmarking-with-tpcc-medium.html",
-              "/${VERSION}/performance-benchmarking-with-tpcc-large.html"
-            ]
-          }
-        ]
-      },
       {
         "title": "Support Resources",
         "urls": [
           "/${VERSION}/support-resources.html"
         ]
       },
-      {
-        "title": "File an Issue",
-        "urls": [
-          "/${VERSION}/file-an-issue.html"
-        ]
-      },
       {
         "title": "Automatic CPU Profiler",
         "urls": [

src/current/_includes/v26.1/topology-patterns/see-also.md

@@ -2,8 +2,6 @@
 - [How to Choose a Multi-Region Configuration]({% link {{ page.version.version }}/choosing-a-multi-region-configuration.md %})
 - [When to Use `ZONE` vs. `REGION` Survival Goals]({% link {{ page.version.version }}/multiregion-survival-goals.md %}#when-to-use-zone-vs-region-survival-goals)
 - [When to Use `REGIONAL` vs. `GLOBAL` Tables]({% link {{ page.version.version }}/table-localities.md %}#when-to-use-regional-vs-global-tables)
-- [Low Latency Reads and Writes in a Multi-Region Cluster]({% link {{ page.version.version }}/demo-low-latency-multi-region-deployment.md %})
-- [Migrate to Multi-Region SQL]({% link {{ page.version.version }}/migrate-to-multiregion-sql.md %})
 - [Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions)
 - [`ALTER DATABASE ... SET SECONDARY REGION`]({% link {{ page.version.version }}/alter-database.md %}#set-secondary-region)
 - [`ALTER DATABASE ... DROP SECONDARY REGION`]({% link {{ page.version.version }}/alter-database.md %}#drop-secondary-region)

src/current/_includes/v26.1/zone-configs/remove-a-replication-zone.md

@@ -1,7 +1,7 @@
 {{site.data.alerts.callout_info}}
 When you discard a zone configuration, the objects it was applied to will then inherit a configuration from an object "the next level up"; e.g., if the object whose configuration is being discarded is a table, it will use its parent database's configuration.
 
-You cannot `DISCARD` any zone configurations on multi-region tables, indexes, or partitions if the [multi-region abstractions]({% link {{ page.version.version }}/migrate-to-multiregion-sql.md %}#replication-zone-patterns-and-multi-region-sql-abstractions) created the zone configuration.
+You cannot `DISCARD` any zone configurations on multi-region tables, indexes, or partitions if the multi-region abstractions created the zone configuration.
 {{site.data.alerts.end}}
 
 {% include_cached copy-clipboard.html %}

src/current/_includes/v26.2/misc/explore-benefits-see-also.md

@@ -1,4 +1,3 @@
 - [Replication & Rebalancing]({% link {{ page.version.version }}/demo-replication-and-rebalancing.md %})
 - [CockroachDB Resilience]({% link {{ page.version.version }}/demo-cockroachdb-resilience.md %})
-- [Low Latency Multi-Region Deployment]({% link {{ page.version.version }}/demo-low-latency-multi-region-deployment.md %})
 - [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})

src/current/_includes/v26.2/prod-deployment/insecure-test-load-balancing.md

@@ -4,10 +4,6 @@ CockroachDB comes with a number of [built-in workloads]({% link {{ page.version.
 Be sure that you have configured your network to allow traffic from the application to the load balancer. In this case, you will run the sample workload on one of your machines. The traffic source should therefore be the **internal (private)** IP address of that machine.
 {{site.data.alerts.end}}
 
-{{site.data.alerts.callout_success}}
-For comprehensive guidance on benchmarking CockroachDB with TPC-C, see [Performance Benchmarking]({% link {{ page.version.version }}/performance-benchmarking-with-tpcc-local.md %}).
-{{site.data.alerts.end}}
-
 1. SSH to the machine where you want the run the sample TPC-C workload.
 
     This should be a machine that is not running a CockroachDB node.

src/current/_includes/v26.2/prod-deployment/prod-see-also.md

@@ -2,6 +2,5 @@
 - [Manual Deployment]({% link {{ page.version.version }}/manual-deployment.md %})
 - [Orchestrated Deployment]({% link {{ page.version.version }}/kubernetes-overview.md %})
 - [Monitoring and Alerting]({% link {{ page.version.version }}/monitoring-and-alerting.md %})
-- [Performance Benchmarking]({% link {{ page.version.version }}/performance-benchmarking-with-tpcc-small.md %})
 - [Performance Tuning]({% link {{ page.version.version }}/performance-best-practices-overview.md %})
 - [Local Deployment]({% link {{ page.version.version }}/start-a-local-cluster.md %})

src/current/_includes/v26.2/prod-deployment/secure-test-load-balancing.md

@@ -4,8 +4,6 @@ CockroachDB comes with a number of [built-in workloads]({% link {{ page.version.
 Be sure that you have configured your network to allow traffic from the application to the load balancer. In this case, you will run the sample workload on one of your machines. The traffic source should therefore be the **internal (private)** IP address of that machine.
 {{site.data.alerts.end}}
 
-For comprehensive guidance on benchmarking CockroachDB with TPC-C, refer to [Performance Benchmarking]({% link {{ page.version.version }}/performance-benchmarking-with-tpcc-local.md %}).
-
 1. SSH to the machine where you want to run the sample TPC-C workload.
 
     This should be a machine that is not running a CockroachDB node, and it should already have a `certs` directory containing `ca.crt`, `client.root.crt`, and `client.root.key` files.

src/current/_includes/v26.2/sidebar-data/multi-region-capabilities.json

@@ -28,6 +28,12 @@
                 "urls": [
                 "/${VERSION}/partitioning.html"
                 ]
+            },
+            {
+                "title": "Data Domiciling with CockroachDB Tutorial",
+                "urls": [
+                "/${VERSION}/data-domiciling.html"
+                ]
             }
             ]
         },
@@ -42,29 +48,6 @@
             "urls": [
             "/${VERSION}/zone-config-extensions.html"
             ]
-        },
-        {
-            "title": "Multi-Region Tutorials",
-            "items": [
-                {
-                    "title": "Low Latency Reads and Writes",
-                    "urls": [
-                    "/${VERSION}/demo-low-latency-multi-region-deployment.html"
-                    ]
-                },
-                {
-                    "title": "Data Domiciling with CockroachDB",
-                    "urls": [
-                    "/${VERSION}/data-domiciling.html"
-                    ]
-                },
-                {
-                    "title": "Migrate to Multi-Region SQL with Replication Zones",
-                    "urls": [
-                    "/${VERSION}/migrate-to-multiregion-sql.html"
-                    ]
-                }
-            ]
         }
     ]
 }

src/current/_includes/v26.2/sidebar-data/reads-and-writes.json

@@ -113,13 +113,6 @@
         "/${VERSION}/local-testing.html"
       ]
     },
-    {
-      "title": "SQL Playground",
-      "is_top_level": true,
-      "urls": [
-        "https://www.cockroachlabs.com/docs/tutorials/sql-playground"
-      ]
-    },
     {
       "title": "Database Management Tools",
       "items": [

src/current/_includes/v26.2/sidebar-data/troubleshooting.json

@@ -80,39 +80,12 @@
           "/${VERSION}/troubleshoot-replication-zones.html"
         ]
       },
-      {
-        "title": "Benchmarking",
-        "items": [
-          {
-            "title": "Overview",
-            "urls": [
-              "/${VERSION}/performance.html"
-            ]
-          },
-          {
-            "title": "Benchmarking with TPC-C",
-            "urls": [
-              "/${VERSION}/performance-benchmarking-with-tpcc-local.html",
-              "/${VERSION}/performance-benchmarking-with-tpcc-local-multiregion.html",
-              "/${VERSION}/performance-benchmarking-with-tpcc-small.html",
-              "/${VERSION}/performance-benchmarking-with-tpcc-medium.html",
-              "/${VERSION}/performance-benchmarking-with-tpcc-large.html"
-            ]
-          }
-        ]
-      },
       {
         "title": "Support Resources",
         "urls": [
           "/${VERSION}/support-resources.html"
         ]
       },
-      {
-        "title": "File an Issue",
-        "urls": [
-          "/${VERSION}/file-an-issue.html"
-        ]
-      },
       {
         "title": "Automatic CPU Profiler",
         "urls": [

src/current/_includes/v26.2/topology-patterns/see-also.md

@@ -2,8 +2,6 @@
 - [How to Choose a Multi-Region Configuration]({% link {{ page.version.version }}/choosing-a-multi-region-configuration.md %})
 - [When to Use `ZONE` vs. `REGION` Survival Goals]({% link {{ page.version.version }}/multiregion-survival-goals.md %}#when-to-use-zone-vs-region-survival-goals)
 - [When to Use `REGIONAL` vs. `GLOBAL` Tables]({% link {{ page.version.version }}/table-localities.md %}#when-to-use-regional-vs-global-tables)
-- [Low Latency Reads and Writes in a Multi-Region Cluster]({% link {{ page.version.version }}/demo-low-latency-multi-region-deployment.md %})
-- [Migrate to Multi-Region SQL]({% link {{ page.version.version }}/migrate-to-multiregion-sql.md %})
 - [Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions)
 - [`ALTER DATABASE ... SET SECONDARY REGION`]({% link {{ page.version.version }}/alter-database.md %}#set-secondary-region)
 - [`ALTER DATABASE ... DROP SECONDARY REGION`]({% link {{ page.version.version }}/alter-database.md %}#drop-secondary-region)

src/current/_includes/v26.2/zone-configs/remove-a-replication-zone.md

@@ -1,7 +1,7 @@
 {{site.data.alerts.callout_info}}
 When you discard a zone configuration, the objects it was applied to will then inherit a configuration from an object "the next level up"; e.g., if the object whose configuration is being discarded is a table, it will use its parent database's configuration.
 
-You cannot `DISCARD` any zone configurations on multi-region tables, indexes, or partitions if the [multi-region abstractions]({% link {{ page.version.version }}/migrate-to-multiregion-sql.md %}#replication-zone-patterns-and-multi-region-sql-abstractions) created the zone configuration.
+You cannot `DISCARD` any zone configurations on multi-region tables, indexes, or partitions if the multi-region abstractions created the zone configuration.
 {{site.data.alerts.end}}
 
 {% include_cached copy-clipboard.html %}

src/current/v26.1/alter-database.md

@@ -729,7 +729,7 @@ ALTER DATABASE movr CONFIGURE ZONE USING range_min_bytes = 0, range_max_bytes =
 {{site.data.alerts.callout_info}}
 When you discard a zone configuration, the objects it was applied to will then inherit a configuration from an object "the next level up"; e.g., if the object whose configuration is being discarded is a table, it will use its parent database's configuration.
 
-You cannot `DISCARD` any zone configurations on multi-region tables, indexes, or partitions if the [multi-region abstractions]({% link {{ page.version.version }}/migrate-to-multiregion-sql.md %}#replication-zone-patterns-and-multi-region-sql-abstractions) created the zone configuration.
+You cannot `DISCARD` any zone configurations on multi-region tables, indexes, or partitions if the [multi-region] ({% link {{ page.version.version }}/multiregion-overview.md %}) created the zone configuration.
 {{site.data.alerts.end}}
 
 {% include_cached copy-clipboard.html %}
@@ -1202,7 +1202,7 @@ To follow along with the examples below:
     cockroach demo --global --nodes 9
     ~~~
 
-1. Set the demo cluster's [database regions]({% link {{ page.version.version }}/multiregion-overview.md %}#database-regions) and [table localities]({% link {{ page.version.version }}/multiregion-overview.md %}#table-locality) as described in [Low Latency Reads and Writes in a Multi-Region Cluster]({% link {{ page.version.version }}/demo-low-latency-multi-region-deployment.md %}) (specifically, starting at [Step 5. Execute multi-region SQL statements]({% link {{ page.version.version }}/demo-low-latency-multi-region-deployment.md %}#step-5-execute-multi-region-sql-statements)).
+1. Set the demo cluster's [database regions]({% link {{ page.version.version }}/multiregion-overview.md %}#database-regions) and [table localities]({% link {{ page.version.version }}/multiregion-overview.md %}#table-locality).
 
 1. Enable the replica placement syntax with either the [session variable]({% link {{ page.version.version }}/set-vars.md %}) or the [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) as shown below.
 

src/current/v26.1/alter-index.md

@@ -243,7 +243,7 @@ ALTER INDEX vehicles@vehicles_auto_index_fk_city_ref_users CONFIGURE ZONE USING
 {{site.data.alerts.callout_info}}
 When you discard a zone configuration, the objects it was applied to will then inherit a configuration from an object "the next level up"; e.g., if the object whose configuration is being discarded is a table, it will use its parent database's configuration.
 
-You cannot `DISCARD` any zone configurations on multi-region tables, indexes, or partitions if the [multi-region abstractions]({% link {{ page.version.version }}/migrate-to-multiregion-sql.md %}#replication-zone-patterns-and-multi-region-sql-abstractions) created the zone configuration.
+You cannot `DISCARD` any zone configurations on multi-region tables, indexes, or partitions if the [multi-region] ({% link {{ page.version.version }}/multiregion-overview.md %}) created the zone configuration.
 {{site.data.alerts.end}}
 
 {% include_cached copy-clipboard.html %}