Merge pull request #6936 from MicrosoftDocs/master

8/23 PM Publish

Author: huypub

docs/2014/relational-databases/indexes/columnstore-indexes-described.md

@@ -21,7 +21,7 @@ ms.author: mikeray
 manager: craigg
 ---
 # Columnstore Indexes Described
-  The [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)]*in-memory columnstore index* stores and manages data by using column-based data storage and column-based query processing. Columnstore indexes work well for data warehousing workloads that primarily perform bulk loads and read-only queries. Use the columnstore index to achieve up to **10x query performance** gains over traditional row-oriented storage, and up to **7x data compression** over the uncompressed data size.  
+  The [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] *in-memory columnstore index* stores and manages data by using column-based data storage and column-based query processing. Columnstore indexes work well for data warehousing workloads that primarily perform bulk loads and read-only queries. Use the columnstore index to achieve up to **10x query performance** gains over traditional row-oriented storage, and up to **7x data compression** over the uncompressed data size.  
 
 > [!NOTE]  
 >  We view the clustered columnstore index as the standard for storing large data warehousing fact tables, and expect it will be used in most data warehousing scenarios. Since the clustered columnstore index is updateable, your workload can perform a large number of insert, update, and delete operations.  

docs/relational-databases/import-export/xml-format-files-sql-server.md

@@ -1,4 +1,4 @@
----
+---
 title: "XML Format Files (SQL Server) | Microsoft Docs"
 ms.custom: ""
 ms.date: "03/14/2017"
@@ -531,7 +531,7 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <RECORD>  
     <FIELD ID="1" xsi:type="CharFixed" LENGTH="10"/>  
     <FIELD ID="2" xsi:type="CharFixed" LENGTH="6"/>  
-    <FIELD ID="3" xsi:type="CharTerm" TERMINATOR="\r\n"  
+    <FIELD ID="3" xsi:type="CharTerm" TERMINATOR="\r\n"/>  
   </RECORD>  
   <ROW>  
     <COLUMN SOURCE="1" NAME="C1" xsi:type="SQLINT" />  

docs/relational-databases/system-stored-procedures/sp-describe-undeclared-parameters-transact-sql.md

@@ -1,7 +1,7 @@
 ---
 title: "sp_describe_undeclared_parameters (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "07/27/2018"
+ms.date: "08/15/2018"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
 ms.component: "system-stored-procedures"
@@ -100,7 +100,7 @@ sp_describe_undeclared_parameters
 
 -   If the input [!INCLUDE[tsql](../../includes/tsql-md.md)] batch declares a local variable of the same name as a parameter declared in \@params.  
 
--   If the statement creates any temporary tables.  
+-   If the statement references temporary tables.  
 
  If \@tsql has no parameters, other than those declared in \@params, the procedure returns an empty result set.  
 

docs/relational-databases/tutorial-signing-stored-procedures-with-a-certificate.md

@@ -1,7 +1,7 @@
 ---
 title: "Tutorial: Signing Stored Procedures with a Certificate | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "08/23/2018"
 ms.prod: sql
 ms.prod_service: "database-engine"
 ms.component: "tutorial"
@@ -17,44 +17,39 @@ helpviewer_keywords:
   - "signing stored procedures tutorial [SQL Server]"
 ms.assetid: a4b0f23b-bdc8-425f-b0b9-e0621894f47e
 caps.latest.revision: 11
-author: "rothja"
-ms.author: "jroth"
+author: "MashaMSFT"
+ms.author: "mathoma"
 manager: craigg
 ---
 # Tutorial: Signing Stored Procedures with a Certificate
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
 This tutorial illustrates signing stored procedures using a certificate generated by [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)].  
 
 > [!NOTE]  
-> To run the code in this tutorial you must have both Mixed Mode security configured and the [!INCLUDE[ssSampleDBobject](../includes/sssampledbobject-md.md)] database installed. Scenario  
+> To run the code in this tutorial you must have both Mixed Mode security configured and the AdventureWorks2017 database installed.   
   
 Signing stored procedures using a certificate is useful when you want to require permissions on the stored procedure but you do not want to explicitly grant a user those rights. Although you can accomplish this task in other ways, such as using the EXECUTE AS statement, using a certificate allows you to use a trace to find the original caller of the stored procedure. This provides a high level of auditing, especially during security or Data Definition Language (DDL) operations.  
 
-You can create a certificate in the master database to allow server-level permissions, or you can create a certificate in any user databases to allow database-level permissions. In this scenario, a user with no rights to base tables must access a stored procedure in the [!INCLUDE[ssSampleDBobject](../includes/sssampledbobject-md.md)] database, and you want to audit the object access trail. Rather than using other ownership chain methods, you will create a server and database user account with no rights to the base objects, and a database user account with rights to a table and a stored procedure. Both the stored procedure and the second database user account will be secured with a certificate. The second database account will have access to all objects, and grant access to the stored procedure to the first database user account.  
+You can create a certificate in the master database to allow server-level permissions, or you can create a certificate in any user databases to allow database-level permissions. In this scenario, a user with no rights to base tables must access a stored procedure in the AdventureWorks2017 database, and you want to audit the object access trail. Rather than using other ownership chain methods, you will create a server and database user account with no rights to the base objects, and a database user account with rights to a table and a stored procedure. Both the stored procedure and the second database user account will be secured with a certificate. The second database account will have access to all objects, and grant access to the stored procedure to the first database user account.  
 
 In this scenario you will first create a database certificate, a stored procedure, and a user, and then you will test the process following these steps:  
 
-1.  Configure the environment.  
-  
-2.  Create a certificate.  
-  
-3.  Create and sign a stored procedure using the certificate.  
-  
-4.  Create a certificate account using the certificate.  
-  
-5.  Grant the certificate account database rights.  
-  
-6.  Display the access context.  
-  
-7.  Reset the environment.  
-  
 Each code block in this example is explained in line. To copy the complete example, see [Complete Example](#CompleteExample) at the end of this tutorial.  
+
+## Prerequisites
+To complete this tutorial, you need SQL Server Management Studio, access to a server that's running SQL Server, and an AdventureWorks database.
+
+- Install [SQL Server Management Studio](https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms).
+- Install [SQL Server 2017 Developer Edition](https://www.microsoft.com/sql-server/sql-server-downloads).
+- Download [AdventureWorks2017 sample databases](https://docs.microsoft.com/sql/samples/adventureworks-install-configure).
+
+Instructions for restoring databases in SSMS are here: [Restore a database](https://docs.microsoft.com/sql/relational-databases/backup-restore/restore-a-database-backup-using-ssms). 
 
 ## 1. Configure the Environment  
-To set the initial context of the example, in [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] open a new Query and run the following code to open the [!INCLUDE[ssSampleDBobject](../includes/sssampledbobject-md.md)] database. This code changes the database context to `AdventureWorks2012` and creates a new server login and database user account (`TestCreditRatingUser`), using a password.  
+To set the initial context of the example, in [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] open a new Query and run the following code to open the Adventureworks2017 database. This code changes the database context to `AdventureWorks2012` and creates a new server login and database user account (`TestCreditRatingUser`), using a password.  
 
-```  
-USE AdventureWorks2012;  
+```sql  
+USE AdventureWorks2017;  
 GO  
 -- Set up a login for the test user  
 CREATE LOGIN TestCreditRatingUser  
@@ -72,18 +67,18 @@ You can create certificates in the server using the master database as the conte
 
 Run this code to create a database certificate and secure it using a password.  
 
-```  
+```sql  
 CREATE CERTIFICATE TestCreditRatingCer  
    ENCRYPTION BY PASSWORD = 'pGFD4bb925DGvbd2439587y'  
       WITH SUBJECT = 'Credit Rating Records Access',   
-      EXPIRY_DATE = '12/05/2014';  
+      EXPIRY_DATE = '12/05/2020';  -- Error 3701 will occur if this date is not in the future
 GO  
 ```  
 
 ## 3. Create and Sign a Stored Procedure Using the Certificate  
 Use the following code to create a stored procedure that selects data from the `Vendor` table in the `Purchasing` database schema, restricting access to only the companies with a credit rating of 1. Note that the first section of the stored procedure displays the context of the user account running the stored procedure, which is to demonstrate the concepts only. It is not required to satisfy the requirements.  
 
-```  
+```sql  
 CREATE PROCEDURE TestCreditRatingSP  
 AS  
 BEGIN  
@@ -105,7 +100,7 @@ GO
 
 Run this code to sign the stored procedure with the database certificate, using a password.  
 
-```  
+```sql  
 ADD SIGNATURE TO TestCreditRatingSP   
    BY CERTIFICATE TestCreditRatingCer  
     WITH PASSWORD = 'pGFD4bb925DGvbd2439587y';  
@@ -119,8 +114,8 @@ For more information on signing stored procedures, see [ADD SIGNATURE (Trans
 ## 4. Create a Certificate Account Using the Certificate  
 Run this code to create a database user (`TestCreditRatingcertificateAccount`) from the certificate. This account has no server login, and will ultimately control access to the underlying tables.  
 
-```  
-USE AdventureWorks2012;  
+```sql  
+USE AdventureWorks2017;  
 GO  
 CREATE USER TestCreditRatingcertificateAccount  
    FROM CERTIFICATE TestCreditRatingCer;  
@@ -130,7 +125,7 @@ GO
 ## 5. Grant the Certificate Account Database Rights  
 Run this code to grant `TestCreditRatingcertificateAccount` rights to the base table and the stored procedure.  
 
-```  
+```sql  
 GRANT SELECT   
    ON Purchasing.Vendor   
    TO TestCreditRatingcertificateAccount;  
@@ -147,7 +142,7 @@ For more information on granting permissions to objects, see [GRANT (Transac
 ## 6. Display the Access Context  
 To display the rights associated with the stored procedure access, run the following code to grant the rights to run the stored procedure to the `TestCreditRatingUser` user.  
 
-```  
+```sql  
 GRANT EXECUTE   
    ON TestCreditRatingSP   
    TO TestCreditRatingUser;  
@@ -156,14 +151,14 @@ GO
 
 Next, run the following code to run the stored procedure as the dbo login you used on the server. Observe the output of the user context information. It will show the dbo account as the context with its own rights and not through a group membership.  
 
-```  
+```sql  
 EXECUTE TestCreditRatingSP;  
 GO  
 ```  
 
 Run the following code to use the `EXECUTE AS` statement to become the `TestCreditRatingUser` account and run the stored procedure. This time you will see the user context is set to the USER MAPPED TO CERTIFICATE context.  
 
-```  
+```sql  
 EXECUTE AS LOGIN = 'TestCreditRatingUser';  
 GO  
 EXECUTE TestCreditRatingSP;  
@@ -178,7 +173,7 @@ This shows you the auditing available because you signed the stored procedure.
 ## 7. Reset the Environment  
 The following code uses the `REVERT` statement to return the context of the current account to dbo, and resets the environment.  
 
-```  
+```sql  
 REVERT;  
 GO  
 DROP PROCEDURE TestCreditRatingSP;  
@@ -198,9 +193,9 @@ For more information about the REVERT statement, see [REVERT (Transact-SQL&#
 ## <a name="CompleteExample"></a>Complete Example  
 This section displays the complete example code.  
 
-```  
-/* Step 1 - Open the AdventureWorks2012 database */  
-USE AdventureWorks2012;  
+```sql  
+/* Step 1 - Open the AdventureWorks2017 database */  
+USE AdventureWorks2017;  
 GO  
 -- Set up a login for the test user  
 CREATE LOGIN TestCreditRatingUser  
@@ -214,7 +209,7 @@ GO
 CREATE CERTIFICATE TestCreditRatingCer  
    ENCRYPTION BY PASSWORD = 'pGFD4bb925DGvbd2439587y'  
       WITH SUBJECT = 'Credit Rating Records Access',   
-      EXPIRY_DATE = '12/05/2014';  
+      EXPIRY_DATE = '12/05/2020';   -- Error 3701 will occur if this date is not in the future
 GO  
 
 /* Step 3 - Create a stored procedure and  

docs/t-sql/statements/alter-database-transact-sql.md

@@ -1,4 +1,4 @@
----
+---
 title: "ALTER DATABASE (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
 ms.date: "08/07/2018"
@@ -44,23 +44,10 @@ In the following row, click whichever product name you are interested in. The cl
 
 ::: moniker range=">=sql-server-2016||>=sql-server-linux-2017||=sqlallproducts-allversions"
 
-> [!div class="mx-tdCol2BreakAll"]
-> <table>
-> <tr>
->   <th> &nbsp; </th>
->   <th> &nbsp; </th>
->   <th> &nbsp; </th>
->   <th> &nbsp; </th>
->   <th> &nbsp; </th>
-> </tr>
-> <tr>
->   <th><strong><em>* SQL Server *<br />&nbsp;</em></strong></th>
->   <th><a href="alter-database-transact-sql.md?view=azuresqldb-current">SQL Database<br />logical server</a></th>
->   <th><a href="alter-database-transact-sql.md?view=azuresqldb-mi-current">SQL Database<br />Managed Instance</a></th>
->   <th><a href="alter-database-transact-sql.md?view=azure-sqldw-latest">SQL Data<br />Warehouse</a></th>
->   <th><a href="alter-database-transact-sql.md?view=aps-pdw-2016">SQL Parallel<br />Data Warehouse</a></th>
-> </tr>
-> </table>
+> [!div class="mx-tdCol2BreakAll"]  
+> ||||||  
+> |---|---|---|---|---|  
+> |**_\* SQL Server \*_** &nbsp;|[SQL Database<br />logical server](alter-database-transact-sql.md?view=azuresqldb-current)|[SQL Database<br />Managed Instance](alter-database-transact-sql.md?view=azuresqldb-mi-current)|[SQL Data<br />Warehouse](alter-database-transact-sql.md?view=azure-sqldw-latest)|[SQL Parallel<br />Data Warehouse](alter-database-transact-sql.md?view=aps-pdw-2016)|  
 
 &nbsp;