Merge pull request #7248 from MicrosoftDocs/master

9/14 PM Publish

Author: huypub

docs/relational-databases/data-tier-applications/dac-support-for-sql-server-objects-and-versions.md

@@ -1,7 +1,7 @@
 ---
 title: "DAC Support For SQL Server Objects and Versions | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "09/13/2018"
 ms.prod: sql
 ms.component: "data-tier-applications"
 ms.reviewer: ""
@@ -20,7 +20,16 @@ manager: craigg
   A data-tier application (DAC) supports the most commonly used [!INCLUDE[ssDE](../../includes/ssde-md.md)] objects.  
 
  **In This Topic**  
-  
+
+
+> [!IMPORTANT]
+> This article is valid for SQL Server 2012, but not for SQL Server 2014 or later.
+> For DAC articles about SQL 2012 and earlier, see the following links:
+>
+> - https://docs.microsoft.com/previous-versions/sql/sql-server-2008-r2/ee240739(v=sql.105)
+> - https://docs.microsoft.com/previous-versions/sql/sql-server-2012/hh753459(v=sql.110)
+
+
 -   [Supported SQL Server Objects](#SupportedObjects)  
 
 -   [Data-tier Application Support by the Versions of SQL Server](#SupportByVersion)  

docs/relational-databases/system-stored-procedures/sp-setapprole-transact-sql.md

@@ -90,7 +90,7 @@ sp_setapprole [ @rolename = ] 'role',
  The following example activates an application role named `SalesAppRole`, with the plain-text password `AsDeF00MbXX`, created with permissions specifically designed for the application used by the current user.  
 
 ```  
-EXEC sp_setapprole 'SalesApprole', 'AsDeF00MbXX';  
+EXEC sys.sp_setapprole 'SalesApprole', 'AsDeF00MbXX';  
 GO  
 ```  
 
@@ -99,12 +99,12 @@ GO
 
 ```  
 DECLARE @cookie varbinary(8000);  
-EXEC sp_setapprole 'Sales11', 'fdsd896#gfdbfdkjgh700mM'  
+EXEC sys.sp_setapprole 'Sales11', 'fdsd896#gfdbfdkjgh700mM'  
     , @fCreateCookie = true, @cookie = @cookie OUTPUT;  
 -- The application role is now active.  
 SELECT USER_NAME();  
 -- This will return the name of the application role, Sales11.  
-EXEC sp_unsetapprole @cookie;  
+EXEC sys.sp_unsetapprole @cookie;  
 -- The application role is no longer active.  
 -- The original context has now been restored.  
 GO  

docs/relational-databases/tables/changing-the-schema-of-a-system-versioned-temporal-table.md

@@ -11,8 +11,8 @@ ms.tgt_pltfrm: ""
 ms.topic: conceptual
 ms.assetid: 9dbe5a21-9335-4f8b-85fd-9da83df79946
 caps.latest.revision: 13
-author: "CarlRabeler"
-ms.author: "carlrab"
+author: CarlRabeler
+ms.author: carlrab
 manager: craigg
 monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
@@ -57,7 +57,7 @@ ALTER TABLE dbo.Department
 
 -   During an **ALTER TABLE** operation, the system holds a schema lock on both tables.  
 
--   Specified schema change is propagated to history table in appropriate way (depending on type of change)  
+-   Specified schema change is propagated to history table appropriately (depending on type of change).  
 
 -   If you add a non-nullable column or alter existing column to become non-nullable, you must specify the default value for existing rows. The system will generate an additional default with the same value and apply it to the history table. Adding **DEFAULT** to a non-empty table is a size of data operation on all editions other than [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Enterprise Edition (on which it is a metadata operation).