Merge pull request #108032 from julieMSFT/sqldw_move1

Sqldw move1

Author: rmca14

.openpublishing.redirection.json

@@ -17054,6 +17054,31 @@
       "redirect_url": "/azure/sql-data-warehouse/maintenance-scheduling#change-a-maintenance-schedule",
       "redirect_document_id": false
     },
+    {
+        "source_path": "articles/sql-data-warehouse/backup-and-restore.md",
+        "redirect_url": "/azure/synapse-analytics/sql-data-warehouse/backup-and-restore",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/sql-data-warehouse/cheat-sheet.md",
+        "redirect_url": "/azure/synapse-analytics/sql-data-warehouse/cheat-sheet",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/sql-data-warehouse/column-level-security.md",
+        "redirect_url": "/azure/synapse-analytics/sql-data-warehouse/column-level-security",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/sql-data-warehouse/create-data-warehouse-portal.md",
+        "redirect_url": "/azure/synapse-analytics/sql-data-warehouse/create-data-warehouse-portal",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/sql-data-warehouse/create-data-warehouse-powershell.md",
+        "redirect_url": "/azure/synapse-analytics/sql-data-warehouse/create-data-warehouse-powershell",
+        "redirect_document_id": true
+    }, 
     {
       "source_path": "articles/sql-data-warehouse/viewing-maintenance-schedule.md",
       "redirect_url": "/azure/sql-data-warehouse/maintenance-scheduling#view-a-maintenance-schedule",

articles/azure-databricks/databricks-extract-load-sql-data-warehouse.md

@@ -41,7 +41,7 @@ If you don’t have an Azure subscription, create a [free account](https://azure
 
 Complete these tasks before you begin this tutorial:
 
-* Create an Azure SQL data warehouse, create a server-level firewall rule, and connect to the server as a server admin. See [Quickstart: Create and query an Azure SQL data warehouse in the Azure portal](../sql-data-warehouse/create-data-warehouse-portal.md).
+* Create an Azure SQL data warehouse, create a server-level firewall rule, and connect to the server as a server admin. See [Quickstart: Create and query an Azure SQL data warehouse in the Azure portal](../synapse-analytics/sql-data-warehouse/create-data-warehouse-portal.md).
 
 * Create a master key for the Azure SQL data warehouse. See [Create a database master key](https://docs.microsoft.com/sql/relational-databases/security/encryption/create-a-database-master-key).
 

articles/cosmos-db/concepts-limits.md

@@ -65,7 +65,7 @@ You can [provision and manage your Azure Cosmos account](how-to-manage-database-
 > [!NOTE]
 > Regional failovers only apply to single region writes accounts. Multi-region write accounts do not require or have any limits on changing the write region.
 
-Cosmos DB automatically takes backups of your data at regular intervals. For details on backup retention intervals and windows, see [Online backup and on-demand data restore in Azure Cosmos DB](online-backup-and-restore.md).
+Cosmos DB automatically takes backups of your data at regular intervals. For details on backup retention intervals and windows, see [Online backup and on-demand data restore in Azure Cosmos DB](../synapse-analytics/sql-data-warehouse/backup-and-restore.md).
 
 ## Per-account limits
 

articles/cosmos-db/database-security.md

@@ -61,8 +61,8 @@ Let's dig into each one in detail.
 |Global replication|Azure Cosmos DB offers turnkey global distribution, which enables you to replicate your data to any one of Azure's world-wide datacenters with the click of a button. Global replication lets you scale globally and provide low-latency access to your data around the world.<br><br>In the context of security, global replication ensures data protection against regional failures.<br><br>Learn more in [Distribute data globally](distribute-data-globally.md).|
 |Regional failovers|If you have replicated your data in more than one data center, Azure Cosmos DB automatically rolls over your operations should a regional data center go offline. You can create a prioritized list of failover regions using the regions in which your data is replicated. <br><br>Learn more in [Regional Failovers in Azure Cosmos DB](high-availability.md).|
 |Local replication|Even within a single data center, Azure Cosmos DB automatically replicates data for high availability giving you the choice of [consistency levels](consistency-levels.md). This replication guarantees a 99.99% [availability SLA](https://azure.microsoft.com/support/legal/sla/cosmos-db) for all single region accounts and all multi-region accounts with relaxed consistency, and 99.999% read availability on all multi-region database accounts.|
-|Automated online backups|Azure Cosmos databases are backed up regularly and stored in a geo redundant store. <br><br>Learn more in [Automatic online backup and restore with Azure Cosmos DB](online-backup-and-restore.md).|
-|Restore deleted data|The automated online backups can be used to recover data you may have accidentally deleted up to ~30 days after the event. <br><br>Learn more in [Automatic online backup and restore with Azure Cosmos DB](online-backup-and-restore.md)|
+|Automated online backups|Azure Cosmos databases are backed up regularly and stored in a geo redundant store. <br><br>Learn more in [Automatic online backup and restore with Azure Cosmos DB](../synapse-analytics/sql-data-warehouse/backup-and-restore.md).|
+|Restore deleted data|The automated online backups can be used to recover data you may have accidentally deleted up to ~30 days after the event. <br><br>Learn more in [Automatic online backup and restore with Azure Cosmos DB](../synapse-analytics/sql-data-warehouse/backup-and-restore.md)|
 |Protect and isolate sensitive data|All data in the regions listed in What's new? is now encrypted at rest.<br><br>Personal data and other confidential data can be isolated to specific container and read-write, or read-only access can be limited to specific users.|
 |Monitor for attacks|By using [audit logging and activity logs](logging.md), you can monitor your account for normal and abnormal activity. You can view what operations were performed on your resources, who initiated the operation, when the operation occurred, the status of the operation, and much more as shown in the screenshot following this table.|
 |Respond to attacks|Once you have contacted Azure support to report a potential attack, a 5-step incident response process is kicked off. The goal of the 5-step process is to restore normal service security and operations as quickly as possible after an issue is detected and an investigation is started.<br><br>Learn more in [Microsoft Azure Security Response in the Cloud](https://aka.ms/securityresponsepaper).|

articles/cosmos-db/etcd-api-introduction.md

@@ -46,7 +46,7 @@ As the Kubernetes cluster grows, the etcd API account in Azure Cosmos DB elastic
 
 ### Security & enterprise readiness
 
-When etcd data is stored in Azure Cosmos DB, Kubernetes developers automatically get the [built-in encryption at rest](database-encryption-at-rest.md),  [certifications and compliance](compliance.md), and [backup and restore capabilities](online-backup-and-restore.md) supported by Azure Cosmos DB. 
+When etcd data is stored in Azure Cosmos DB, Kubernetes developers automatically get the [built-in encryption at rest](database-encryption-at-rest.md),  [certifications and compliance](compliance.md), and [backup and restore capabilities](../synapse-analytics/sql-data-warehouse/backup-and-restore.md) supported by Azure Cosmos DB. 
 
 ## Next steps
 

articles/cosmos-db/faq.md

@@ -398,7 +398,7 @@ You can add as many regions as you want for the account and control where it can
 
 ### Is the Table API enabled for backups?
 
-Yes, the Table API leverages the platform of Azure Cosmos DB for backups. Backups are made automatically. For more information, see [Online backup and restore with Azure Cosmos DB](online-backup-and-restore.md).
+Yes, the Table API leverages the platform of Azure Cosmos DB for backups. Backups are made automatically. For more information, see [Online backup and restore with Azure Cosmos DB](../synapse-analytics/sql-data-warehouse/backup-and-restore.md).
 
 ### Does the Table API index all attributes of an entity by default?
 
@@ -756,7 +756,7 @@ At present Azure Cosmos DB has an optimized experience for cloud environment wit
 ### Does Cassandra API provide full backups?
 
 Azure Cosmos DB provides two free full backups taken at four hours interval today across all APIs. This ensures you don't need to set up a backup schedule and other things.
-If you want to modify retention and frequency, send an email to [[email protected]](mailto:[email protected]) or raise a support case. Information about backup capability is provided in the [Automatic online backup and restore with Azure Cosmos DB](online-backup-and-restore.md) article.
+If you want to modify retention and frequency, send an email to [[email protected]](mailto:[email protected]) or raise a support case. Information about backup capability is provided in the [Automatic online backup and restore with Azure Cosmos DB](../synapse-analytics/sql-data-warehouse/backup-and-restore.md) article.
 
 ### How does the Cassandra API account handle failover if a region goes down?
 

articles/cosmos-db/how-to-setup-cmk.md

@@ -228,7 +228,7 @@ Not currently, but container-level keys are being considered.
 
 ### How do customer-managed keys affect a backup?
 
-Azure Cosmos DB takes [regular and automatic backups](./online-backup-and-restore.md) of the data stored in your account. This operation backs up the encrypted data. To use the restored backup, the encryption key that you used at the time of the backup is required. This means that no revocation was made and the version of the key that was used at the time of the backup will still be enabled.
+Azure Cosmos DB takes [regular and automatic backups](../synapse-analytics/sql-data-warehouse/backup-and-restore.md) of the data stored in your account. This operation backs up the encrypted data. To use the restored backup, the encryption key that you used at the time of the backup is required. This means that no revocation was made and the version of the key that was used at the time of the backup will still be enabled.
 
 ### How do I revoke an encryption key?
 

articles/cosmos-db/online-backup-and-restore.md

@@ -86,7 +86,7 @@ Delete the restored accounts as soon as you are done migrating, because they wil
 Next you can learn about how to restore data from an Azure Cosmos account or learn how to migrate data to an Azure Cosmos account
 
 * To make a restore request, contact Azure Support, [file a ticket from the Azure portal](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade)
-* [How to restore data from an Azure Cosmos account](how-to-backup-and-restore.md)
+* [How to restore data from an Azure Cosmos account](../synapse-analytics/sql-data-warehouse/backup-and-restore.md)
 * [Use Cosmos DB change feed](change-feed.md) to move data to Azure Cosmos DB.
 * [Use Azure Data Factory](../data-factory/connector-azure-cosmos-db.md) to move data to Azure Cosmos DB.
 

articles/cosmos-db/optimize-cost-throughput.md

@@ -151,7 +151,7 @@ The following steps help you to make your solutions highly scalable and cost-eff
 
 1. If you have significantly over provisioned throughput across containers and databases, you should review RUs provisioned Vs consumed RUs and fine-tune the workloads.  
 
-2. One method for estimating the amount of reserved throughput required by your application is to record the request unit RU charge associated with running typical operations against a representative Azure Cosmos container or database used by your application and then estimate the number of operations you anticipate to perform each second. Be sure to measure and include typical queries and their usage as well. To learn how to estimate RU costs of queries programmatically or using portal see [Optimizing the cost of queries](online-backup-and-restore.md). 
+2. One method for estimating the amount of reserved throughput required by your application is to record the request unit RU charge associated with running typical operations against a representative Azure Cosmos container or database used by your application and then estimate the number of operations you anticipate to perform each second. Be sure to measure and include typical queries and their usage as well. To learn how to estimate RU costs of queries programmatically or using portal see [Optimizing the cost of queries](../synapse-analytics/sql-data-warehouse/backup-and-restore.md). 
 
 3. Another way to get operations and their costs in RUs is by enabling Azure Monitor logs, which will give you the breakdown of operation/duration and the request charge. Azure Cosmos DB provides request charge for every operation, so every operation charge can be stored back from the response and then used for analysis. 
 

articles/machine-learning/algorithm-module-reference/module-reference.md

@@ -19,7 +19,7 @@ Each module represents a set of code that can run independently and perform a ma
 
 For help with choosing algorithms, see 
 * [How to select algorithms](../how-to-select-algorithms.md)
-* [Azure Machine Learning Algorithm Cheat Sheet](../algorithm-cheat-sheet.md)
+* [Azure Machine Learning Algorithm Cheat Sheet](../../synapse-analytics/sql-data-warehouse/cheat-sheet.md)
 
 > [!TIP]
 > In any pipeline in the designer, you can get information about a specific module. Select the module, then select the **more help** link in the **Quick Help** pane.