Merge pull request #72248 from julieMSFT/20190405_SQLDB_SEO

seoapril2019

Author: GitHubber17

articles/sql-database/saas-tenancy-app-design-patterns.md

@@ -12,12 +12,13 @@ ms.author: genemi
 ms.reviewer: billgib, sstein
 manager: craigg
 ms.date: 01/25/2019
+ms.custom: seoapril2019
 ---
 # Multi-tenant SaaS database tenancy patterns
 
-When designing a multi-tenant SaaS application, you must carefully choose the tenancy model that best fits the needs of your application.  A tenancy model determines how each tenant’s data is mapped to storage.  Your choice of tenancy model impacts application design and management.  Switching to a different model later is sometimes costly.
+This article describes the various tenancy models available for a multi-tenant SaaS application.
 
-This article describes alternative tenancy models.
+When designing a multi-tenant SaaS application, you must carefully choose the tenancy model that best fits the needs of your application.  A tenancy model determines how each tenant’s data is mapped to storage.  Your choice of tenancy model impacts application design and management.  Switching to a different model later is sometimes costly.
 
 ## A. SaaS concepts and terminology
 

articles/sql-database/sql-database-elastic-pool-manage.md

@@ -1,5 +1,5 @@
 ---
-title: Create and manage elastic pools - Azure SQL database | Microsoft Docs
+title: Manage elastic pools - Azure SQL database | Microsoft Docs
 description: Create and manage Azure SQL elastic pools.
 services: sql-database
 ms.service: sql-database
@@ -12,9 +12,10 @@ ms.author: moslake
 ms.reviewer: carlrab
 manager: craigg
 ms.date: 03/12/2019
+ms.custom: seoapril2019
 ---
 
-# Create and manage elastic pools in Azure SQL Database
+# Manage elastic pools in Azure SQL Database
 
 With an elastic pool, you determine the amount of resources that the elastic pool requires to handle the workload of its databases, and the amount of resources for each pooled database.
 

articles/sql-database/sql-database-managed-instance-transact-sql-information.md

@@ -1,26 +1,22 @@
 ---
-title: Azure SQL Database Managed Instance T-SQL Differences | Microsoft Docs
+title: Azure SQL Database-Managed Instance T-SQL Differences | Microsoft Docs
 description: This article discusses the T-SQL differences between a Managed Instance in Azure SQL Database and SQL Server
 services: sql-database
 ms.service: sql-database
 ms.subservice: managed-instance
-ms.custom: 
 ms.devlang: 
 ms.topic: conceptual
 author: jovanpop-msft
 ms.author: jovanpop
 ms.reviewer: carlrab, bonova 
 manager: craigg
 ms.date: 03/13/2019
+ms.custom: seoapril2019
 ---
 
 # Azure SQL Database Managed Instance T-SQL differences from SQL Server
 
-The Managed Instance deployment option provides high compatibility with on-premises SQL Server Database Engine. Most of the SQL Server database engine features are supported in a Managed Instance.
-
-![migration](./media/sql-database-managed-instance/migration.png)
-
-Since there are still some differences in syntax and behavior, this article summarizes and explains these differences. <a name="Differences"></a>
+This article summarizes and explains the differences in syntax and behavior between Azure SQL Database Managed Instance and on-premises SQL Server Database Engine. <a name="Differences"></a>
 
 - [Availability](#availability) including the differences in [Always-On](#always-on-availability) and [Backups](#backup),
 - [Security](#security) including the differences in [Auditing](#auditing), [Certificates](#certificates), [Credentials](#credential), [Cryptographic providers](#cryptographic-providers), [Logins / users](#logins--users), [Service key and service master key](#service-key-and-service-master-key),
@@ -29,6 +25,10 @@ Since there are still some differences in syntax and behavior, this article summ
 - [Features that have different behavior in Managed Instances](#Changes)
 - [Temporary limitations and known issues](#Issues)
 
+The Managed Instance deployment option provides high compatibility with on-premises SQL Server Database Engine. Most of the SQL Server database engine features are supported in a Managed Instance.
+
+![migration](./media/sql-database-managed-instance/migration.png)
+
 ## Availability
 
 ### <a name="always-on-availability"></a>Always-On
@@ -468,7 +468,7 @@ The following variables, functions, and views return different results:
 
 ### TEMPDB size
 
-Max file size of `tempdb` cannot be greather than 24GB/core on General Purpose tier. Max `tempdb` size on Business Critical tier is limited with the instance storage size. `tempdb` is always split into 12 data files. This maximum size per file can't be changed and new files can be added to `tempdb`. Some queries might return an error if  they need more than 24GB / core in `tempdb`.
+Max file size of `tempdb` cannot be greater than 24GB/core on General Purpose tier. Max `tempdb` size on Business Critical tier is limited with the instance storage size. `tempdb` is always split into 12 data files. This maximum size per file can't be changed and new files can be added to `tempdb`. Some queries might return an error if  they need more than 24GB / core in `tempdb`.
 
 ### Cannot restore contained database
 
@@ -489,7 +489,7 @@ This illustrates that under certain circumstance, due to a specific distribution
 
 In this example, existing databases will continue to work and can grow without any problem as long as new files are not added. However new databases could not be created or restored because there is not enough space for new disk drives, even if the total size of all databases does not reach the instance size limit. The error that is returned in that case is not clear.
 
-You can [identify number of remaining files](https://medium.com/azure-sqldb-managed-instance/how-many-files-you-can-create-in-general-purpose-azure-sql-managed-instance-e1c7c32886c1) using system views. If you are reaching this limit try to [empty and delete some of the smaller files using DBCC SHRINKFILE statement](https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-shrinkfile-transact-sql#d-emptying-a-file) or shitch to [Business Critical tier that don't has this limit](https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-resource-limits#service-tier-characteristics).
+You can [identify number of remaining files](https://medium.com/azure-sqldb-managed-instance/how-many-files-you-can-create-in-general-purpose-azure-sql-managed-instance-e1c7c32886c1) using system views. If you are reaching this limit try to [empty and delete some of the smaller files using DBCC SHRINKFILE statement](https://docs.microsoft.com/sql/t-sql/database-console-commands/dbcc-shrinkfile-transact-sql#d-emptying-a-file) or switch to [Business Critical tier that don't has this limit](https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-resource-limits#service-tier-characteristics).
 
 ### Incorrect configuration of SAS key during database restore
 

articles/sql-database/toc.yml

@@ -168,7 +168,7 @@
         href: sql-database-dtu-resource-limits-elastic-pools.md  
       - name: Scale resources
         href: sql-database-elastic-pool-scale.md
-    - name: Create and manage
+    - name: Manage pool resources
       href: sql-database-elastic-pool-manage.md
   - name: Managed instances
     items: