double log throughput rate

freshness pass

testing columns

testing h4s

Author: MashaMSFT

azure-sql/managed-instance/doc-changes-updates-release-notes-whats-new.md

@@ -5,8 +5,7 @@ description: Learn about the new features and documentation improvements for Azu
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: wiassaf
-ms.date: 08/04/2023
-
+ms.date: 08/21/2023
 ms.service: sql-managed-instance
 ms.subservice: service-overview
 ms.topic: whats-new

docs/dma/dma-overview.md

@@ -1,98 +1,117 @@
 ---
 title: "Overview of Data Migration Assistant (SQL Server)"
-description: Learn how to use Data Migration Assistant to migrate SQL Server databases to other SQL Server or Azure databases
+description: Learn how to use Data Migration Assistant to migrate SQL Server databases to other instances of SQL Server or Azure SQL Database.
 author: ajithkr-ms
 ms.author: ajithkr
 ms.reviewer: randolphwest
-ms.date: 05/24/2022
+ms.date: 08/21/2023
 ms.service: sql
 ms.subservice: dma
-ms.topic: conceptual
-helpviewer_keywords:
+ms.topic: overview
+ms.custom: UpdateFrequency5
+helpviewer_keywords: 
   - "Data Migration Assistant, overview"
 ---
 
 # Overview of Data Migration Assistant
 
-The Data Migration Assistant (DMA) helps you upgrade to a modern data platform by detecting compatibility issues that can impact database functionality in your new version of SQL Server or Azure SQL Database. DMA recommends performance and reliability improvements for your target environment and allows you to move your schema, data, and uncontained objects from your source server to your target server.
+The Data Migration Assistant (DMA) helps you upgrade to a modern data platform by detecting compatibility issues that can impact database functionality when you upgrade to a new version of SQL Server or migrate to [Azure SQL Database](/azure/azure-sql/database/sql-database-paas-overview).  DMA recommends performance and reliability improvements for your target environment and allows you to move your schema, data, and uncontained objects from your source server to your target server.
 
 > [!NOTE]
-> For large migrations (in terms of number and size of databases), we recommend that you use the [Azure Database Migration Service](/azure/dms/dms-overview), which can migrate databases at scale.
+> - For SQL Server large migrations (in terms of number and size of databases) to Azure, we recommend that you use the [Azure Database Migration Service](/azure/dms/dms-overview), which can migrate databases at scale.
+> - DMA does not support database migrations to [Azure SQL Managed Instance](/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview). Use the [Azure SQL migration extension for Azure Data Studio](/azure/dms/migration-using-azure-data-studio) instea, which supports both online and offline database migrations to Azure SQL Managed Instance.
   
 ## Get Data Migration Assistant
 
 To install DMA, download the latest version of the tool from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=53595), and then run the **DataMigrationAssistant.msi** file.
 
 ## Capabilities
 
-- Assess on-premises SQL Server instance(s) migrating to Azure SQL database(s). The assessment workflow helps you to detect the following issues that can affect Azure SQL database migration and provides detailed guidance on how to resolve them.
+DMA brings you the following capabilities: 
 
-  - Migration blocking issues: Discovers the compatibility issues that block migrating on-premises SQL Server database(s) to Azure SQL Database(s). DMA provides recommendations to help you address those issues.
+#### Assess on-premises SQL Server Instances migrating to Azure
 
-  - Partially supported or unsupported features: Detects partially supported or unsupported features that are currently in use on the source SQL Server instance. DMA provides a comprehensive set of recommendations, alternative approaches available in Azure, and mitigating steps so that you can incorporate them into your migration projects.
+Assess on-premises SQL Server instance(s) migrating to Azure SQL Database or Azure SQL Managed Instance. The assessment workflow helps you to detect the following issues which may affect your Azure SQL migration and provides detailed guidance on how to resolve them.
 
-- Discover issues that can affect an upgrade to an on-premises SQL Server. These are described as compatibility issues and are organized in the following categories:
+  - Migration blocking issues: Discovers the compatibility issues that block migrating on-premises SQL Server database to Azure SQL Database. DMA provides recommendations to help you address those issues.
+
+  - Partially supported or unsupported features: Detects partially supported or unsupported features that are currently in use by the source SQL Server instance. DMA provides a comprehensive set of recommendations, alternative approaches available in Azure, and mitigating steps so that you can incorporate them into your migration projects.
+
+#### Discover issues that affect an upgrade
+
+Discover issues that can affect an upgrade to an on-premises SQL Server. These are described as compatibility issues and are organized in the following categories:
 
   - Breaking changes
   - Behavior changes
   - Deprecated features
 
-- Discover new features in the target SQL Server platform that the database can benefit from after an upgrade. These are described as feature recommendations and are organized in the following categories:
+#### Discover new features
+
+Discover new features in the target SQL Server platform that the database can benefit from after an upgrade. These are described as feature recommendations and are organized in the following categories:
 
   - Performance
   - Security
   - Storage
 
-- Migrate an on-premises SQL Server instance to a modern SQL Server instance hosted on-premises or on an Azure virtual machine (VM) that is accessible from your on-premises network. The Azure VM can be accessed using VPN or other technologies. The migration workflow helps you to migrate the following components:
+#### Migrate on-premises instances to SQL Server on Azure VMs
+
+Migrate an on-premises SQL Server instance to a modern SQL Server instance hosted on-premises or on an Azure virtual machine (VM) that is accessible from your on-premises network. The Azure VM can be accessed using VPN or other technologies. The migration workflow helps you to migrate the following components:
 
   - Schema of databases
   - Data and users
   - Server roles
   - SQL Server and Windows logins
 
-- After a successful migration, applications can connect to the target SQL Server databases seamlessly.
+#### Assess on-premesis SSIS packages migration to Azure
 
-- Assess on-premises SQL Server Integration Services (SSIS) package(s) migrating to Azure SQL Database or Azure SQL Managed Instance. The assessment helps to discover issues that can affect the migration. These are described as compatibility issues and are organized in the following categories:
+Assess on-premises SQL Server Integration Services (SSIS) package(s) migrating to Azure SQL Database or Azure SQL Managed Instance. The assessment helps to discover issues that can affect the migration. These are described as compatibility issues and are organized in the following categories:
 
   - Migration blockers: discovers the compatibility issues that block migrating source package(s) to Azure. DMA provides recommendations to help you address those issues.
 
   - Information issues: detects partially supported or deprecated features that are used in source package(s).
 
-> [!NOTE]  
-> DMA does not support database migrations to Azure SQL Managed Instance. Recommendation is to use the [Azure SQL migration extension for Azure Data Studio](/azure/dms/migration-using-azure-data-studio), which supports both online and offline database migrations to Azure SQL Managed Instance.
+#### Connect to databases after migration
+
+After a successful migration, applications can connect to the target SQL databases seamlessly.
 
-## Prerequisites
+
+## Permissions
 
 To run an assessment, you have to be a member of the SQL Server **sysadmin** role. The recommended display resolution is 1024x756.
 
 ## Supported source and target versions
 
-DMA replaces all previous versions of SQL Server Upgrade Advisor and should be used for upgrades for most SQL Server versions. Supported source and target versions for assessment are:
-
-### Sources
-
-- SQL Server 2005 (deprecated)
-- SQL Server 2008
-- SQL Server 2008 R2
-- SQL Server 2012
-- SQL Server 2014
-- SQL Server 2016
-- SQL Server 2017
-- SQL Server 2019
-- SQL Server 2022
-- Amazon RDS for SQL Server
-
-### Targets
-
-- SQL Server 2012
-- SQL Server 2014
-- SQL Server 2016
-- SQL Server 2017 on Windows and Linux
-- SQL Server 2019
-- SQL Server 2022
-- Azure SQL Database single database
-- Azure SQL Managed Instance (assessment only)
-- SQL Server running on an Azure Virtual Machine
+DMA replaces all previous versions of SQL Server Upgrade Advisor and should be used for upgrades for most SQL Server versions. The following list shows the supported source and target versions for assessment: 
+
+
+:::row:::
+    :::column:::
+    **Supported sources**
+    - SQL Server 2005 (deprecated)
+    - SQL Server 2008
+    - SQL Server 2008 R2
+    - SQL Server 2012
+    - SQL Server 2014
+    - SQL Server 2016
+    - SQL Server 2017
+    - SQL Server 2019
+    - SQL Server 2022
+    - Amazon RDS for SQL Server
+    :::column-end:::
+    :::column:::
+    **Supported targets**
+    - SQL Server 2012
+    - SQL Server 2014
+    - SQL Server 2016
+    - SQL Server 2017 on Windows and Linux
+    - SQL Server 2019 on Windows and Linux
+    - SQL Server 2022 on Windows and Linux
+    - [Azure SQL Database](/azure/azure-sql/database/sql-database-paas-overview)
+    - [Azure SQL Managed Instance](/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview) (assessment only)
+    - [SQL Server on Azure Virtual Machines](/azure/azure-sql/virtual-machines/windows/sql-server-on-azure-vm-iaas-what-is-overview)
+    :::column-end:::
+:::row-end:::
+
 
 ## See also
 

docs/relational-databases/tables/delete-columns-from-a-table.md

@@ -3,10 +3,11 @@ title: "Delete columns from a table"
 description: "Delete columns from a table"
 author: WilliamDAssafMSFT
 ms.author: wiassaf
-ms.date: "12/15/2021"
+ms.date: "08/21/2023"
 ms.service: sql
 ms.subservice: table-view-index
-ms.topic: conceptual
+ms.topic: how-to
+ms.custom: UpdateFrequency5
 helpviewer_keywords:
   - "columns [SQL Server], deleting"
   - "removing columns"
@@ -27,7 +28,8 @@ This article describes how to delete table columns in [!INCLUDE[ssnoversion](../
 
 You can't delete a column that has a CHECK constraint. You must first delete the constraint.
 
-You can't delete a column that has PRIMARY KEY or FOREIGN KEY constraints or other dependencies except when using the [Table Designer](../../ssms/visual-db-tools/visual-database-tool-designers.md#table-designer) in SSMS. When using [Object Explorer](../../ssms/object/object-explorer.md) or [!INCLUDE[tsql](../../includes/tsql-md.md)], you must first remove all dependencies on the column.
+You can't delete a column that has PRIMARY KEY or FOREIGN KEY constraints or other dependencies except when using the [Table Designer](../../ssms/visual-db-tools/visual-database-tool-designers.md#table-designer) in SSMS. When using [Object Explorer](../../ssms/object/object-explorer.md) in SSMS or [!INCLUDE[tsql](../../includes/tsql-md.md)], you must first remove all dependencies on the column.
+
 ## <a name="Permissions"></a> Permissions
 
 Requires ALTER permission on the table.
@@ -36,12 +38,12 @@ Requires ALTER permission on the table.
 
 The following steps explain how to delete columns with Object Explorer in SSMS:
 
-1. In **Object Explorer**, connect to an instance of [!INCLUDE[ssDE](../../includes/ssde-md.md)].
-2. In **Object Explorer**, locate the table from which you want to delete columns, and expand to expose the column names.
+1. Connect to an instance of [!INCLUDE[ssDE](../../includes/ssde-md.md)].
+2. In **Object Explorer**, locate the table from which you want to delete columns, and expand the table to expose the column names.
 3. Right-click the column that you want to delete, and choose **Delete**.
-4. In **Delete Object** dialog box, click **OK**.
+4. In the **Delete Object** dialog box, click **OK**.
 
-If the column contains constraints or other dependencies, an error message will display in the **Delete Object** dialog box. Resolve the error by deleting the referenced constraints.
+If the column contains constraints or other dependencies, an error message displays in the **Delete Object** dialog box. Resolve the error by deleting the referenced constraints.
 
 ## Delete columns using Table Designer
 

docs/relational-databases/tables/specify-default-values-for-columns.md

@@ -3,10 +3,11 @@ title: "Specify Default Values for Columns"
 description: "Specify Default Values for Columns"
 author: WilliamDAssafMSFT
 ms.author: wiassaf
-ms.date: 10/21/2021
+ms.date: 08/21/2023
 ms.service: sql
 ms.subservice: table-view-index
-ms.topic: conceptual
+ms.topic: how-to
+ms.custom: UpdateFrequency5
 helpviewer_keywords:
   - "columns [SQL Server], defaults"
   - "default values"
@@ -16,7 +17,7 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 
 [!INCLUDE [sqlserver2016-asdb-asdbmi-asa-pdw](../../includes/applies-to-version/sqlserver2016-asdb-asdbmi-asa-pdw.md)]
 
-You can use [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] to specify a default value that will be entered into the table column. You can set a default by using the SQL Server Management Studio (SSMS) Object Explorer or by executing [!INCLUDE[tsql](../../includes/tsql-md.md)].
+You can use [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] to specify a default value that will be entered into the table column. You can set a default by using the SSMS Object Explorer or by executing [!INCLUDE[tsql](../../includes/tsql-md.md)].
 
 If you do not assign a default value to the column, and the user leaves the column blank, then:
 
@@ -29,11 +30,8 @@ If you do not assign a default value to the column, and the user leaves the colu
 Before you begin, be aware of the following limitations and restrictions:
 
 - If your entry in the **Default Value** field replaces a bound default (which is shown without parentheses), you will be prompted to unbind the default and replace it with your new default.
-
 - To enter a text string, enclose the value in single quotation marks ('); do not use double quotation marks (") because they are reserved for quoted identifiers.
-
 - To enter a numeric default, enter the number without quotation marks around it.
-
 - To enter an object/function, enter the name of the object/function without quotation marks around it.
 
 > [!NOTE]
@@ -45,10 +43,9 @@ The actions described in this article require **ALTER** permission on the table.
 
 ## <a name="SSMSProcedure"></a> Use SSMS to specify a default
 
-You can use the Object Explorer to specify a default value for a table column.
-
-### Object Explorer
+You can use Object Explorer in SSMS to specify a default value for a table column. To do so, follow these steps: 
 
+1. Connect to your SQL Server instance in SSMS. 
 1. In **Object Explorer**, right-click the table with columns for which you want to change the scale and select **Design**.
 
 2. Select the column for which you want to specify a default value.
@@ -62,7 +59,7 @@ You can use the Object Explorer to specify a default value for a table column.
 
 ## <a name="TsqlProcedure"></a> Use Transact-SQL to specify a default
 
-There are various ways that you can specify a default value for a column, by using SSMS to submit T-SQL.
+There are various ways that you can specify a default value for a column by using submit T-SQL.
 
 ### ALTER TABLE (T-SQL)
 

docs/sql-server/previous-versions-sql-server.md

@@ -3,7 +3,7 @@ title: Previous versions of SQL Server documentation
 description: How to get online and offline documentation for previous versions of SQL Server, including 2005, 2008, 2012, and 2014.
 author: markingmyname
 ms.author: maghan
-ms.date: 08/12/2020
+ms.date: 08/21/2023
 ms.service: sql
 ms.subservice: install
 ms.topic: conceptual