Merge pull request from MicrosoftDocs/master

atikmapari · web-flow · commit 708ed6d76382 · 2021-01-13T02:23:36.000+05:30
Sync with master
diff --git a/azure-sql/database/automated-backups-overview.md b/azure-sql/database/automated-backups-overview.md
@@ -116,7 +116,7 @@ Backup storage consumption up to the maximum data size for a database is not cha
 
 ## Backup retention
 
-For all new, restored, and copied databases, Azure SQL Database and Azure SQL Managed Instance retain sufficient backups to allow PITR within the last 7 days by default. With the exception of Hyperscale databases, you can [change backup retention period](#change-the-pitr-backup-retention-period) per each active database in the 1-35 day range. As described in [Backup storage consumption](#backup-storage-consumption), backups stored to enable PITR may be older than the retention period. For Azure SQL Managed Instance only, it is possible to set the PITR backup retention rate once a database has been deleted in the 0-35 days range. 
+For all new, restored, and copied databases, Azure SQL Database and Azure SQL Managed Instance retain sufficient backups to allow PITR within the last 7 days by default. With the exception of Hyperscale and Basic tier databases, you can [change backup retention period](#change-the-pitr-backup-retention-period) per each active database in the 1-35 day range. As described in [Backup storage consumption](#backup-storage-consumption), backups stored to enable PITR may be older than the retention period. For Azure SQL Managed Instance only, it is possible to set the PITR backup retention rate once a database has been deleted in the 0-35 days range. 
 
 If you delete a database, the system keeps backups in the same way it would for an online database with its specific retention period. You cannot change backup retention period for a deleted database.
 
diff --git a/azure-sql/database/data-discovery-and-classification-overview.md b/azure-sql/database/data-discovery-and-classification-overview.md
@@ -22,7 +22,7 @@ Data Discovery & Classification is built into Azure SQL Database, Azure SQL Mana
 Your most sensitive data might include business, financial, healthcare, or personal information. Discovering and classifying this data can play a pivotal role in your organization's information-protection approach. It can serve as infrastructure for:
 
 - Helping to meet standards for data privacy and requirements for regulatory compliance.
-- Various security scenarios, such as monitoring (auditing) and alerting on anomalous access to sensitive data.
+- Various security scenarios, such as monitoring (auditing) access to sensitive data.
 - Controlling access to and hardening the security of databases that contain highly sensitive data.
 
 > [!NOTE]
@@ -181,4 +181,4 @@ You can use the REST API to programmatically manage classifications and recommen
 ## <a id="next-steps"></a>Next steps
 
 - Consider configuring [Azure SQL Auditing](../../azure-sql/database/auditing-overview.md) for monitoring and auditing access to your classified sensitive data.
-- For a presentation that includes data Discovery & Classification, see [Discovering, classifying, labeling & protecting SQL data | Data Exposed](https://www.youtube.com/watch?v=itVi9bkJUNc).
+- For a presentation that includes data Discovery & Classification, see [Discovering, classifying, labeling & protecting SQL data | Data Exposed](https://www.youtube.com/watch?v=itVi9bkJUNc).
diff --git a/azure-sql/database/database-copy.md b/azure-sql/database/database-copy.md
@@ -129,6 +129,46 @@ CREATE DATABASE Database2 AS COPY OF server1.Database1;
 
 You can use the steps in the [Copy a SQL Database to a different server](#copy-to-a-different-server) section to copy your database to a server in a different subscription using T-SQL. Make sure you use a login that has the same name and password as the database owner of the source database. Additionally, the login must be a member of the `dbmanager` role or a server administrator, on both source and target servers.
 
+```sql
+Step# 1
+Create login and user in the master database of the source server.
+
+CREATE LOGIN loginname WITH PASSWORD = 'xxxxxxxxx'
+GO
+CREATE USER [loginname] FOR LOGIN [loginname] WITH DEFAULT_SCHEMA=[dbo]
+GO
+
+Step# 2
+Create the user in the source database and grant dbowner permission to the database.
+
+CREATE USER [loginname] FOR LOGIN [loginname] WITH DEFAULT_SCHEMA=[dbo]
+GO
+exec sp_addrolemember 'db_owner','loginname'
+GO
+
+Step# 3
+Capture the SID of the user “loginname” from master database
+
+SELECT [sid] FROM sysusers WHERE [name] = 'loginname'
+
+Step# 4
+Connect to Destination server.
+Create login and user in the master database, same as of the source server.
+
+CREATE LOGIN loginname WITH PASSWORD = 'xxxxxxxxx', SID = [SID of loginname login on source server]
+GO
+CREATE USER [loginname] FOR LOGIN [loginname] WITH DEFAULT_SCHEMA=[dbo]
+GO
+exec sp_addrolemember 'dbmanager','loginname'
+GO
+
+Step# 5
+Execute the copy of database script from the destination server using the credentials created
+
+CREATE DATABASE new_database_name
+AS COPY OF source_server_name.source_database_name
+```
+
 > [!NOTE]
 > The [Azure portal](https://portal.azure.com), PowerShell, and the Azure CLI do not support database copy to a different subscription.
 
diff --git a/azure-sql/database/database-export.md b/azure-sql/database/database-export.md
@@ -9,7 +9,7 @@ author: stevestein
 ms.custom: sqldbrb=2
 ms.author: sstein
 ms.reviewer: 
-ms.date: 07/16/2019
+ms.date: 01/11/2021
 ms.topic: how-to
 ---
 # Export to a BACPAC file - Azure SQL Database and Azure SQL Managed Instance
@@ -24,6 +24,7 @@ When you need to export a database for archiving or for moving to another platfo
 - If you are exporting to blob storage, the maximum size of a BACPAC file is 200 GB. To archive a larger BACPAC file, export to local storage.
 - Exporting a BACPAC file to Azure premium storage using the methods discussed in this article is not supported.
 - Storage behind a firewall is currently not supported.
+- Storage file name or the input value for StorageURI should be less than 128 characters long and cannot end with '.' and cannot contain special characters like a space character or '<,>,*,%,&,:,\,/,?'. 
 - If the export operation exceeds 20 hours, it may be canceled. To increase performance during export, you can:
 
   - Temporarily increase your compute size.
@@ -106,4 +107,4 @@ $exportStatus
 - To learn about exporting a BACPAC from a SQL Server database, see [Export a Data-tier Application](/sql/relational-databases/data-tier-applications/export-a-data-tier-application)
 - To learn about using the Data Migration Service to migrate a database, see [Migrate from SQL Server to Azure SQL Database offline using DMS](../../dms/tutorial-sql-server-to-azure-sql.md).
 - If you are exporting from SQL Server as a prelude to migration to Azure SQL Database, see [Migrate a SQL Server database to Azure SQL Database](migrate-to-database-from-sql-server.md).
-- To learn how to manage and share storage keys and shared access signatures securely, see [Azure Storage Security Guide](../../storage/blobs/security-recommendations.md).
+- To learn how to manage and share storage keys and shared access signatures securely, see [Azure Storage Security Guide](../../storage/blobs/security-recommendations.md).
diff --git a/azure-sql/database/dynamic-data-masking-configure-portal.md b/azure-sql/database/dynamic-data-masking-configure-portal.md
@@ -18,7 +18,7 @@ ms.date: 04/28/2020
 This article shows you how to implement [dynamic data masking](dynamic-data-masking-overview.md) with the Azure portal. You can also implement dynamic data masking using [Azure SQL Database cmdlets](/powershell/module/az.sql/) or the [REST API](/rest/api/sql/).
 
 > [!NOTE]
-> This feature cannot be set using portal for Azure Synapse (use PowerShell or REST API) or SQL Managed Instance. For more information, see [Dynamic Data Masking](/sql/relational-databases/security/dynamic-data-masking).
+> This feature cannot be set using portal for SQL Managed Instance (use PowerShell or REST API). For more information, see [Dynamic Data Masking](/sql/relational-databases/security/dynamic-data-masking).
 
 ## Set up dynamic data masking for your database using the Azure portal
 
@@ -54,4 +54,4 @@ This article shows you how to implement [dynamic data masking](dynamic-data-mask
 ## Next steps
 
 - For an overview of dynamic data masking, see [dynamic data masking](dynamic-data-masking-overview.md).
-- You can also implement dynamic data masking using [Azure SQL Database cmdlets](/powershell/module/az.sql/) or the [REST API](/rest/api/sql/).
+- You can also implement dynamic data masking using [Azure SQL Database cmdlets](/powershell/module/az.sql/) or the [REST API](/rest/api/sql/).
diff --git a/azure-sql/database/elastic-query-getting-started-vertical.md b/azure-sql/database/elastic-query-getting-started-vertical.md
@@ -71,6 +71,7 @@ INSERT INTO [dbo].[CustomerInformation] ([CustomerID], [CustomerName], [Company]
     SECRET = '<password>';  
     ```
 
+    The "master_key_password" is a strong password of your choosing used to encrypt the connection credentials. 
     The "username" and "password" should be the username and password used to log in into the Customers database.
     Authentication using Azure Active Directory with elastic queries is not currently supported.
 
@@ -123,4 +124,4 @@ For pricing information, see [SQL Database Pricing](https://azure.microsoft.com/
 * For syntax and sample queries for vertically partitioned data, see [Querying vertically partitioned data)](elastic-query-vertical-partitioning.md)
 * For a horizontal partitioning (sharding) tutorial, see [Getting started with elastic query for horizontal partitioning (sharding)](elastic-query-getting-started.md).
 * For syntax and sample queries for horizontally partitioned data, see [Querying horizontally partitioned data)](elastic-query-horizontal-partitioning.md)
-* See [sp\_execute \_remote](/sql/relational-databases/system-stored-procedures/sp-execute-remote-azure-sql-database) for a stored procedure that executes a Transact-SQL statement on a single remote Azure SQL Database or set of databases serving as shards in a horizontal partitioning scheme.
+* See [sp\_execute \_remote](/sql/relational-databases/system-stored-procedures/sp-execute-remote-azure-sql-database) for a stored procedure that executes a Transact-SQL statement on a single remote Azure SQL Database or set of databases serving as shards in a horizontal partitioning scheme.
diff --git a/azure-sql/database/elastic-scale-introduction.md b/azure-sql/database/elastic-scale-introduction.md
@@ -17,7 +17,7 @@ You can easily scale out databases in Azure SQL Database using the **Elastic Dat
 
 * [Elastic Database client library](elastic-database-client-library.md): The client library is a feature that allows you to create and maintain sharded databases.  See [Get started with Elastic Database tools](elastic-scale-get-started.md).
 * [Elastic Database split-merge tool](elastic-scale-overview-split-and-merge.md): moves data between sharded databases. This tool is useful for moving data from a multi-tenant database to a single-tenant database (or vice-versa). See [Elastic database Split-Merge tool tutorial](elastic-scale-configure-deploy-split-and-merge.md).
-* [Elastic Database jobs](elastic-jobs-overview.md): Use jobs to manage large numbers of databases in Azure SQL Database. Easily perform administrative operations such as schema changes, credentials management, reference data updates, performance data collection, or tenant (customer) telemetry collection using jobs.
+* [Elastic Database jobs](elastic-jobs-overview.md) (preview): Use jobs to manage large numbers of databases in Azure SQL Database. Easily perform administrative operations such as schema changes, credentials management, reference data updates, performance data collection, or tenant (customer) telemetry collection using jobs.
 * [Elastic Database query](elastic-query-overview.md) (preview): Enables you to run a Transact-SQL query that spans multiple databases. This enables connection to reporting tools such as Excel, Power BI, Tableau, etc.
 * [Elastic transactions](elastic-transactions-overview.md): This feature allows you to run transactions that span several databases. Elastic database transactions are available for .NET applications using ADO .NET and integrate with the familiar programming experience using the [System.Transaction classes](/dotnet/api/system.transactions).
 
@@ -97,4 +97,4 @@ To see the specifics of the elastic pool, see [Price and performance considerati
 [1]:./media/elastic-scale-introduction/tools.png
 [2]:./media/elastic-scale-introduction/h_versus_vert.png
 [3]:./media/elastic-scale-introduction/overview.png
-[4]:./media/elastic-scale-introduction/single_v_multi_tenant.png
+[4]:./media/elastic-scale-introduction/single_v_multi_tenant.png
diff --git a/azure-sql/database/policy-reference.md b/azure-sql/database/policy-reference.md
@@ -1,7 +1,7 @@
 ---
 title: Built-in policy definitions for Azure SQL Database
 description: Lists Azure Policy built-in policy definitions for Azure SQL Database and SQL Managed Instance. These built-in policy definitions provide common approaches to managing your Azure resources.
-ms.date: 11/20/2020
+ms.date: 01/08/2021
 ms.topic: reference
 author: stevestein
 ms.author: sstein
diff --git a/azure-sql/database/quota-increase-request.md b/azure-sql/database/quota-increase-request.md
@@ -104,6 +104,7 @@ If your subscription needs access in a particular region, select the **Region ac
 
    ![Request region access](./media/quota-increase-request/quota-request.png)
 
+<!--
 ### <a id="mseries"></a> Enable M-series access to a region
 
 To enable M-series hardware for a subscription and region, a support request must be opened.
@@ -114,6 +115,7 @@ To enable M-series hardware for a subscription and region, a support request mus
 
 
    ![Request M-series region access](./media/quota-increase-request/quota-m-series.png)
+-->
 
 ## <a id="sqlmiquota"></a> SQL Managed Instance quota type
 
diff --git a/azure-sql/database/security-controls-policy.md b/azure-sql/database/security-controls-policy.md
@@ -1,7 +1,7 @@
 ---
 title: Azure Policy Regulatory Compliance controls for Azure SQL Database
 description: Lists Azure Policy Regulatory Compliance controls available for Azure SQL Database and SQL Managed Instance. These built-in policy definitions provide common approaches to managing the compliance of your Azure resources.
-ms.date: 11/20/2020
+ms.date: 01/08/2021
 ms.topic: sample
 author: stevestein
 ms.author: sstein
diff --git a/azure-sql/database/sql-database-vulnerability-assessment-storage.md b/azure-sql/database/sql-database-vulnerability-assessment-storage.md
@@ -5,8 +5,8 @@ services: sql-database
 ms.service: sql-db-mi
 ms.subservice: security
 ms.topic: how-to
-author: barmichal
-ms.author: mibar
+author: davidtrigano
+ms.author: datrigan
 ms.reviewer: vanto
 ms.date: 12/01/2020
 ---
@@ -18,18 +18,21 @@ If you are limiting access to your storage account in Azure for certain VNets or
 
 ## Enable Azure SQL Database VA scanning access to the storage account
 
-If you have configured your VA storage account to only be accessible by certain networks or services, you'll need to ensure that VA scans for your Azure SQL Database are able to store the scans on the storage account. To find out which storage account is being used, go to your **SQL server** pane in the [Azure portal](https://portal.azure.com), under **Security**, select **Security Center**.
+If you have configured your VA storage account to only be accessible by certain networks or services, you'll need to ensure that VA scans for your Azure SQL Database are able to store the scans on the storage account. You can use the existing storage account, or create a new storage account to store VA scan results for all databases on your [logical SQL server](logical-servers.md).
 
-:::image type="content" source="../database/media/azure-defender-for-sql/va-storage.png" alt-text="set up vulnerability assessment":::
-
-You can use the existing storage account, or create a new storage account to store VA scan results for all databases on your [logical SQL server](logical-servers.md).
+> [!NOTE]
+> The vulnerability assessment service can't access storage accounts protected with firewalls or VNets if they require storage access keys.
 
 Go to your **Resource group** that contains the storage account and access the **Storage account** pane. Under **Settings**, select **Firewall and virtual networks**.
 
 Ensure that **Allow trusted Microsoft services access to this storage account** is checked.
 
 :::image type="content" source="media/sql-database-vulnerability-assessment-storage/storage-allow-microsoft-services.png" alt-text="Screenshot shows Firewall and virtual networks dialog box, with Allow trusted Microsoft services to access this storage account selected.":::
 
+To find out which storage account is being used, go to your **SQL server** pane in the [Azure portal](https://portal.azure.com), under **Security**, select **Security Center**.
+
+:::image type="content" source="../database/media/azure-defender-for-sql/va-storage.png" alt-text="set up vulnerability assessment":::
+
 ## Store VA scan results for Azure SQL Managed Instance in a storage account that can be accessed behind a firewall or VNet
 
 Since Managed Instance is not a trusted Microsoft Service and has a different VNet from the storage account, executing a VA scan will result in an error.
@@ -58,4 +61,4 @@ You should now be able to store your VA scans for Managed Instances in your stor
 
 - [Vulnerability Assessment](sql-vulnerability-assessment.md)
 - [Create an Azure Storage account](../../storage/common/storage-account-create.md)
-- [Azure Defender for SQL](azure-defender-for-sql.md)
+- [Azure Defender for SQL](azure-defender-for-sql.md)
diff --git a/azure-sql/virtual-machines/windows/availability-group-manually-configure-prerequisites-tutorial.md b/azure-sql/virtual-machines/windows/availability-group-manually-configure-prerequisites-tutorial.md
@@ -537,7 +537,7 @@ Repeat the steps on the other SQL Server VM.
 
 ### Tuning Failover Cluster Network Thresholds
 
-When running Windows Failover Cluster nodes in Azure Vms with SQL Server AlwaysOn, changing the cluster setting to a more relaxed monitoring state is recommended.  This will make the cluster much more stable and reliable.  For details on this, see [IaaS with SQL AlwaysOn - Tuning Failover Cluster Network Thresholds](/windows-server/troubleshoot/iaas-sql-failover-cluster).
+When running Windows Failover Cluster nodes in Azure Vms with SQL Server availability groups, change the cluster setting to a more relaxed monitoring state.  This will make the cluster much more stable and reliable.  For details on this, see [IaaS with SQL Server - Tuning Failover Cluster Network Thresholds](/windows-server/troubleshoot/iaas-sql-failover-cluster).
 
 
 ## <a name="endpoint-firewall"></a> Configure the firewall on each SQL Server VM
diff --git a/azure-sql/virtual-machines/windows/availability-group-overview.md b/azure-sql/virtual-machines/windows/availability-group-overview.md
@@ -61,7 +61,7 @@ To get started, see [configure a load balancer](availability-group-vnn-azure-loa
 
 ### DNN listener
 
-SQL Server 2019 CU8 introduces support for the distributed network name (DNN) listener. The DNN listener replaces the traditional availability group listener, negating the need for an Azure Loud Balancer to route traffic on the Azure network. 
+SQL Server 2019 CU8 introduces support for the distributed network name (DNN) listener. The DNN listener replaces the traditional availability group listener, negating the need for an Azure Load Balancer to route traffic on the Azure network. 
 
 The DNN listener is the recommended HADR connectivity solution in Azure as it simplifies deployment, reduces maintenance and cost, and reduces failover time in the event of a failure. 
 
