Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into release-remove-sscurrent-tag

Author: v-alje

docs/connect/spark/connector.md

@@ -45,8 +45,6 @@ You can also build the connector from source or download the jar from the Releas
 | Microsoft SQL Server                 | SQL Server 2008 or later        |
 | Azure SQL Databases                  | Supported                       |
 
-> [!NOTE]
-> Azure Synapse Analytics use is not tested with this connector. While it may work, there may be unintended consequences.
 
 ### Supported Options
 The Apache Spark Connector for SQL Server and Azure SQL supports the options defined here: [SQL DataSource JDBC](https://spark.apache.org/docs/latest/sql-data-sources-jdbc.html)

docs/relational-databases/indexes/move-an-existing-index-to-a-different-filegroup.md

@@ -2,7 +2,7 @@
 description: "Move an Existing Index to a Different Filegroup"
 title: "Move an Existing Index to a Different Filegroup | Microsoft Docs"
 ms.custom: ""
-ms.date: "02/17/2017"
+ms.date: "05/11/2021"
 ms.prod: sql
 ms.prod_service: "database-engine"
 ms.reviewer: ""
@@ -18,28 +18,17 @@ ms.assetid: 167ebe77-487d-4ca8-9452-4b2c7d5cb96e
 author: MikeRayMSFT
 ms.author: mikeray
 ---
-# Move an Existing Index to a Different Filegroup
+# Move an existing index to a different filegroup
+
  [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
   This topic describes how to move an existing index from its current filegroup to a different filegroup in [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] by using [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or [!INCLUDE[tsql](../../includes/tsql-md.md)].  
+
+For design considerations including why you might want to place a nonclustered index on a different filegroup, see [Index Placement on Filegroups or Partitions Schemes](../sql-server-index-design-guide.md#Index_placement).
+
+##  <a name="BeforeYouBegin"></a> Before you begin  
 
- **In This Topic**  
-  
--   **Before you begin:**  
-  
-     [Limitations and Restrictions](#Restrictions)  
-  
-     [Security](#Security)  
-  
--   **To move an existing index to a different filegroup, using:**  
-  
-     [SQL Server Management Studio](#SSMSProcedure)  
-  
-     [Transact-SQL](#TsqlProcedure)  
-  
-##  <a name="BeforeYouBegin"></a> Before You Begin  
-  
-###  <a name="Restrictions"></a> Limitations and Restrictions  
+###  <a name="Restrictions"></a> Limitations and restrictions  
 
 -   If a table has a clustered index, moving the clustered index to a new filegroup moves the table to that filegroup.  
 
@@ -50,7 +39,7 @@ ms.author: mikeray
 ####  <a name="Permissions"></a> Permissions  
  Requires ALTER permission on the table or view. User must be a member of the **sysadmin** fixed server role or the **db_ddladmin** and **db_owner** fixed database roles.  
 
-##  <a name="SSMSProcedure"></a> Using SQL Server Management Studio  
+##  <a name="SSMSProcedure"></a> Use SQL Server Management Studio  
 
 #### To move an existing index to a different filegroup using Table Designer  
 
@@ -177,7 +166,9 @@ ms.author: mikeray
         ON TransactionsFG1;  
     GO  
     ```  
+
+## Next steps
+
+For more information, see [CREATE INDEX &#40;Transact-SQL&#41;](../../t-sql/statements/create-index-transact-sql.md).  
   
- For more information, see [CREATE INDEX &#40;Transact-SQL&#41;](../../t-sql/statements/create-index-transact-sql.md).  
-  
-  
+[SQL Server Index Architecture and Design Guide](../sql-server-index-design-guide.md)

docs/relational-databases/performance/database-engine-tuning-advisor.md

@@ -1,21 +1,20 @@
 ---
-title: "Database Engine Tuning Advisor | Microsoft Docs"
+title: "Database Engine Tuning Advisor"
 description: Learn how to use Database Engine Tuning Advisor to troubleshoot, tune a large set of queries, analyze design changes, and manage storage space in SQL Server.
 ms.custom: ""
-ms.date: "01/09/2017"
+ms.date: "05/11/2021"
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: performance
 ms.topic: conceptual
 f1_keywords: 
   - "sql13.dta.general.f1"
-ms.assetid: 50dd0a0b-a407-4aeb-bc8b-b02a793aa30a
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ---
 # Database Engine Tuning Advisor
  [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
-  The [!INCLUDE[msCoName](../../includes/msconame-md.md)] Database Engine Tuning Advisor (DTA) analyzes databases and makes recommendations that you can use to optimize query performance. You can use the Database Engine Tuning Advisor to select and create an optimal set of indexes, indexed views, or table partitions without having an expert understanding of the database structure or the internals of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Using the DTA, you can perform the following tasks.  
+  The [!INCLUDE[msCoName](../../includes/msconame-md.md)] Database Engine Tuning Advisor (DTA) analyzes databases and makes recommendations that you can use to optimize query performance. You can use the Database Engine Tuning Advisor to select and create an optimal set of indexes, indexed views, or table partitions without having an expert understanding of the database structure or the internals of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Using the DTA, you can perform the following tasks:
 
 -   Troubleshoot the performance of a specific problem query  
 
@@ -25,7 +24,11 @@ ms.author: wiassaf
 
 -   Manage storage space  
 
-## Database Engine Tuning Advisor Benefits  
+  
+> [!NOTE]
+> The Database Engine Tuning Advisor is not supported for [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)] or [!INCLUDE[ssazuremi_md](../../includes/ssazuremi_md.md)]. Instead, consider the strategies recommended in [Monitoring and performance tuning in Azure SQL Database and Azure SQL Managed Instance](/azure/azure-sql/database/monitor-tune-overview). For [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)], see also the [Database Advisor performance recommendations for Azure SQL Database](/azure/azure-sql/database/database-advisor-implement-performance-recommendations).
+
+## Database Engine Tuning Advisor benefits  
  Optimizing query performance can be difficult without a full understanding the database structure and the queries that are run against the database. The **Database Engine Tuning Advisor (DTA)** can make this task easier by analyzing the current query plan cache or by analyzing a workload of [!INCLUDE[tsql](../../includes/tsql-md.md)] queries that you create and recommending an appropriate physical design. For more advanced database administrators, DTA exposes a powerful mechanism to perform exploratory what-if analysis of different physical design alternatives. The DTA can provide the following information.  
 
 -   Recommend the best mix of rowstore and [columnstore](../../relational-databases/performance/columnstore-index-recommendations-in-database-engine-tuning-advisor-dta.md) indexes for databases by using the query optimizer to analyze queries in a workload.  
@@ -95,7 +98,7 @@ The Database Engine Tuning Advisor is designed to handle the following types of
 
     3.  The user who runs Database Engine Tuning Advisor is not a member of the **db_owner** database role or the **sysadmin** fixed server role. The queries in the workload are analyzed in the security context of the user who runs the Database Engine Tuning Advisor. The user must be a member of the **db_owner** database role.  
 
--   Database Engine Tuning Advisor stores tuning session data and other information in the **msdb** database. If changes are made to the **msdb** database you may risk losing tuning session data. To eliminate this risk, implement an appropriate backup strategy for the **msdb** database.  
+-   Database Engine Tuning Advisor stores tuning session data and other information in the `msdb` database. If changes are made to the `msdb` database, you may risk losing tuning session data. To eliminate this risk, implement an appropriate backup strategy for the `msdb` database.  
 
 ## Performance Considerations  
  Database Engine Tuning Advisor can consume significant processor and memory resources during analysis. To avoid slowing down your production server, follow one of these strategies:  
@@ -106,15 +109,15 @@ The Database Engine Tuning Advisor is designed to handle the following types of
 
 -   Specify only the physical database design structures you want Database Engine Tuning Advisor to analyze. Database Engine Tuning Advisor provides many options, but specifies only those that are necessary.  
 
-## Dependency on xp_msver Extended Stored Procedure  
+## Dependency on xp_msver extended stored procedure  
  Database Engine Tuning Advisor depends on the **xp_msver** extended stored procedure to provide full functionality. This extended stored procedure is turned on by default. Database Engine Tuning Advisor uses this extended stored procedure to fetch the number of processors and available memory on the computer where the database that you are tuning resides. If **xp_msver** is unavailable, Database Engine Tuning Advisor assumes the hardware characteristics of the computer where Database Engine Tuning Advisor is running. If the hardware characteristics of the computer where Database Engine Tuning Advisor is running are not available, one processor and 1024 megabytes (MBs) of memory are assumed.  
 
  This dependency affects partitioning recommendations because the number of partitions recommended depends on these two values (number of processors and available memory). The dependency also affects your tuning results when you use a test server to tune your production server. In this scenario, Database Engine Tuning Advisor uses **xp_msver** to fetch hardware properties from the production server. After tuning the workload on the test server, Database Engine Tuning Advisor uses these hardware properties to generate a recommendation. For more information, see [xp_msver (Transact-SQL)](../../relational-databases/system-stored-procedures/xp-msver-transact-sql.md).  
 
-## Database Engine Tuning Advisor Tasks  
- The following table lists common Database Engine Tuning Advisor tasks and the topics that describe how to perform them.  
+## Database Engine Tuning Advisor tasks  
+ The following table lists common Database Engine Tuning Advisor tasks and the articles that describe how to perform them.  
 
-|Database Engine Tuning Advisor Task|Topic|  
+|Database Engine Tuning Advisor task|article|  
 |-----------------------------------------|-----------|  
 |Initialize and start the Database Engine Tuning Advisor.<br /><br /> Create a workload by specifying the plan cache, by creating a script, or by generating a trace file or trace table.<br /><br /> Tune a database by using the Database Engine Tuning Advisor graphical user interface tool.<br /><br /> Create XML input files to tune workloads.<br /><br /> View descriptions of the Database Engine Tuning Advisor user interface options.|[Start and Use the Database Engine Tuning Advisor](../../relational-databases/performance/start-and-use-the-database-engine-tuning-advisor.md)|  
 |View the results of the database tuning operation.<br /><br /> Select and implement tuning recommendations.<br /><br /> Perform what-if exploratory analysis against the workload.<br /><br /> Review existing tuning sessions, clone sessions based on existing ones <br />or edit existing tuning recommendations for further evaluation or implementation.<br /><br /> View descriptions of the Database Engine Tuning Advisor user interface options.|[View and Work with the Output from the Database Engine Tuning Advisor](../../relational-databases/performance/view-and-work-with-the-output-from-the-database-engine-tuning-advisor.md)|