moving things around

Author: MashaMSFT

articles/azure-sql/database/scale-resources.md

@@ -1,6 +1,6 @@
 ---
 title: Scale Resources
-description: This article explains how to scale your database in Azure SQL Database by adding or removing allocated resources.
+description: This article explains how to scale your database in Azure SQL Database and SQL Managed Instance by adding or removing allocated resources.
 services: sql-database
 ms.service: sql-database
 ms.subservice: performance
@@ -16,19 +16,19 @@ ms.date: 06/25/2019
 # Dynamically scale database resources with minimal downtime
 [!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
-Azure SQL Database enables you to dynamically add more resources to your database with minimal [downtime](https://azure.microsoft.com/support/legal/sla/sql-database); however, there is a switch over period where connectivity is lost to the database for a short amount of time, which can be mitigated using retry logic.
+Azure SQL Database and SQL Managed Instance enable you to dynamically add more resources to your database with minimal [downtime](https://azure.microsoft.com/support/legal/sla/sql-database); however, there is a switch over period where connectivity is lost to the database for a short amount of time, which can be mitigated using retry logic.
 
 ## Overview
 
-When demand for your app grows from a handful of devices and customers to millions, Azure SQL Database scales on the fly with minimal downtime. Scalability is one of the most important characteristics of PaaS that enables you to dynamically add more resources to your service when needed. Azure SQL Database enables you to easily change resources (CPU power, memory, IO throughput, and storage) allocated to your databases.
+When demand for your app grows from a handful of devices and customers to millions, Azure SQL Database and SQL Managed Instance scales on the fly with minimal downtime. Scalability is one of the most important characteristics of PaaS that enables you to dynamically add more resources to your service when needed. Azure SQL Database enables you to easily change resources (CPU power, memory, IO throughput, and storage) allocated to your databases.
 
 You can mitigate performance issues due to increased usage of your application that cannot be fixed using indexing or query rewrite methods. Adding more resources enables you to quickly react when your database hits the current resource limits and needs more power to handle the incoming workload. Azure SQL Database also enables you to scale-down the resources when they are not needed to lower the cost.
 
 You don’t need to worry about purchasing hardware and changing underlying infrastructure. Scaling database can be easily done via Azure portal using a slider.
 
 ![Scale database performance](./media/scale-resources/scale-performance.svg)
 
-Azure SQL Database offers the [DTU-based purchasing model](service-tiers-dtu.md) and the [vCore-based purchasing model](service-tiers-vcore.md).
+Azure SQL Database offers the [DTU-based purchasing model](service-tiers-dtu.md) and the [vCore-based purchasing model](service-tiers-vcore.md), while Azure SQL Managed Instance offers just the [vCore-based purchasing model](service-tiers-vcore.md). 
 
 - The [DTU-based purchasing model](service-tiers-dtu.md) offers a blend of compute, memory, and IO resources in three service tiers to support lightweight to heavyweight database workloads: Basic, Standard, and Premium. Performance levels within each tier provide a different mix of these resources, to which you can add additional storage resources.
 - The [vCore-based purchasing model](service-tiers-vcore.md) lets you choose the number of vCores, the amount or memory, and the amount and speed of storage. This purchasing model offers three service tiers: General Purpose, Business Critical, and Hyperscale.
@@ -38,19 +38,22 @@ You can build your first app on a small, single database at a low cost per month
 > [!NOTE]
 > Dynamic scalability is different from autoscale. Autoscale is when a service scales automatically based on criteria, whereas dynamic scalability allows for manual scaling with a minimal downtime.
 
-Single Azure SQL Database supports manual dynamic scalability, but not autoscale. For a more *automatic* experience, consider using elastic pools, which allow databases to share resources in a pool based on individual database needs.
+Single databases in Azure SQL Database support manual dynamic scalability, but not autoscale. For a more *automatic* experience, consider using elastic pools, which allow databases to share resources in a pool based on individual database needs.
 However, there are scripts that can help automate scalability for a single Azure SQL Database. For an example, see [Use PowerShell to monitor and scale a single SQL Database](scripts/monitor-and-scale-database-powershell.md).
 
 You can change [DTU service tiers](service-tiers-dtu.md) or [vCore characteristics](resource-limits-vcore-single-databases.md) at any time with minimal downtime to your application (generally averaging under four seconds). For many businesses and apps, being able to create databases and dial performance up or down on demand is enough, especially if usage patterns are relatively predictable. But if you have unpredictable usage patterns, it can make it hard to manage costs and your business model. For this scenario, you use an elastic pool with a certain number of eDTUs that are shared among multiple databases in the pool.
 
 ![Intro to SQL Database: Single database DTUs by tier and level](./media/scale-resources/single_db_dtus.png)
 
-All three flavors of Azure SQL Database offer some ability to dynamically scale your databases:
+Azure SQL Database offers the ability to dynamically scale your databases:
 
 - With a [single database](single-database-scale.md), you can use either [DTU](resource-limits-dtu-single-databases.md) or [vCore](resource-limits-vcore-single-databases.md) models to define maximum amount of resources that will be assigned to each database.
-- A [Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md) uses [vCores](../managed-instance/sql-managed-instance-paas-overview.md#vcore-based-purchasing-model) mode and enables you to define maximum CPU cores and maximum of storage allocated to your instance. All databases within the instance will share the resources allocated to the instance.
 - [Elastic pools](elastic-pool-scale.md) enable you to define maximum resource limit per group of databases in the pool.
 
+Azure SQL Managed Instance allows you to scale as well: 
+
+- A [SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md) uses [vCores](../managed-instance/sql-managed-instance-paas-overview.md#vcore-based-purchasing-model) mode and enables you to define maximum CPU cores and maximum of storage allocated to your instance. All databases within the instance will share the resources allocated to the instance.
+
 Initiating scale up or scale down action in any of the flavors would restart database engine process and move it to a different virtual machine if needed. Moving database engine process to a new virtual machine is **online process** where you can continue using your existing Azure SQL Database service while the process is in progress. Once the target database engine is fully initialized and ready to process the queries, the connections will be [switched from source to target database engine](single-database-scale.md#impact).
 
 > [!NOTE]
@@ -67,5 +70,5 @@ Scaling resources is the easiest and the most effective way to improve performan
 
 - For information about improving database performance by changing database code, see [Find and apply performance recommendations](database-advisor-find-recommendations-portal.md).
 - For information about letting built-in database intelligence optimize your database, see [Automatic tuning](automatic-tuning-overview.md).
-- For information about Read Scale-out in the Azure SQL Database service, see how to [use read-only replicas to load balance read-only query workloads](read-scale-out.md).
+- For information about Read Scale-out in Azure SQL Database, see how to [use read-only replicas to load balance read-only query workloads](read-scale-out.md).
 - For information about a Database sharding, see [Scaling out with Azure SQL Database](elastic-scale-introduction.md).

articles/azure-sql/multi-model-features.md

@@ -12,8 +12,8 @@ ms.author: jovanpop
 ms.reviewer:
 ms.date: 12/17/2018
 ---
-# Multi-model capabilities of Microsoft Azure SQL
-[!INCLUDE[appliesto-asf](includes/appliesto-asf.md)]
+# Multi-model capabilities of Azure SQL Database & SQL Managed Instance
+[!INCLUDE[appliesto-sqldb-sqlmi](includes/appliesto-sqldb-sqlmi.md)]
 
 Multi-model databases enable you to store and work with data represented in multiple data formats such as relational data, graphs, JSON/XML documents, key-value pairs, and so on.
 

articles/azure-sql/toc.yml

@@ -1,49 +1,44 @@
 - name: Azure SQL Documentation
   href: index.yml
 
-- name: Azure SQL
-  items: 
-  - name: What is Azure SQL? 
-    href: azure-sql-iaas-vs-paas-what-is-overview.md
-  - name: Multi-model features
-    href: multi-model-features.md
-
+- name: What is Azure SQL? 
+  href: azure-sql-iaas-vs-paas-what-is-overview.md
 
 - name: Shared SQL DB & SQL MI docs 
   items:
-  - name: Shared concepts 
-    itemS: 
-    - name: Feature comparison
-      href: database/features-comparison.md    
-    - name: Azure Hybrid Benefit
-      href: azure-hybrid-benefit.md
-    - name: Accelerated database recovery
-      href: accelerated-database-recovery.md
-    - name: In-memory OLTP
-      href: in-memory-oltp-overview.md
-    - name: Temporal tables
-      href: temporal-tables.md
-
-    - name: Purchasing models
-      items:
-      - name: Overview
-        href: database/purchasing-models.md
-      - name: vCore model overview
-        href: database/service-tiers-vcore.md
-      - name: Reserved capacity
-        href: database/reserved-capacity-overview.md
-
-    - name: Compute & storage
+  - name: Azure Hybrid Benefit
+    href: azure-hybrid-benefit.md
+  - name: Purchasing models
+    items:
+    - name: Overview
+      href: database/purchasing-models.md
+    - name: vCore model overview
+      href: database/service-tiers-vcore.md
+    - name: Reserved capacity
+      href: database/reserved-capacity-overview.md
+  - name: Compute & storage
       items:
       - name: Overview
         href: database/service-tiers-general-purpose-business-critical.md
         displayName: provisioned compute tier
       - name: General purpose / Standard
         href: database/service-tier-general-purpose.md
       - name: Business critical / Premium
-        href: database/service-tier-business-critical.md
-      - name: Scale Up/Down
-        href: database/scale-resources.md
+        href: database/service-tier-business-critical.md        
+
+  - name: Shared concepts 
+    itemS: 
+    - name: Feature comparison
+      href: database/features-comparison.md
+    - name: Multi-model features
+      href: multi-model-features.md      
+
+    - name: In-memory OLTP
+      href: in-memory-oltp-overview.md
+    - name: Temporal tables
+      href: temporal-tables.md
+    - name: Scale up / down
+      href: database/scale-resources.md
 
     - name: Security
       items:
@@ -87,18 +82,20 @@
           href: database/data-discovery-and-classification-overview.md
 
     - name: Business continuity
-      displayName: Backup, back up, restore
+      displayName: Backup, back up, restore, recovery
       items:
         - name: Overview
           href: database/business-continuity-high-availability-disaster-recover-hadr-overview.md
         - name: High availability
           href: database/high-availability-sla.md
         - name: Auto-failover groups
           href: database/auto-failover-group-overview.md
-        - name: Backups
+        - name: Backup and recovery 
           items:
           - name: Automated backups
             href: database/automated-backups-overview.md
+          - name: Accelerated database recovery
+            href: accelerated-database-recovery.md 
           - name: Recovery using backups
             href: database/recovery-using-backups.md
           - name: Long-term backup retention