Bringing even with master.

Author: v-alje

.openpublishing.redirection.json

@@ -13849,6 +13849,16 @@
             "source_path": "docs/powershell/sql-server-powershell-license-terms.md",
             "redirect_url": "https://docs.microsoft.com/Legal/sql/sql-server-powershell-license-terms",
             "redirect_document_id": true
+        },
+        {
+            "source_path": "docs/ssdt/install-sql-server-data-tools.md",
+            "redirect_url": "/sql/ssdt/download-sql-server-data-tools-ssdt",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/ssdt/removing-sql-server-data-tools-components.md",
+            "redirect_url": "/sql/ssdt/download-sql-server-data-tools-ssdt",
+            "redirect_document_id": false
         }
     ]
 }

docs/integration-services/lift-shift/ssis-azure-connect-with-windows-auth.md

@@ -1,7 +1,7 @@
 ---
 title: "sys.dm_db_resource_stats (Azure SQL Database) | Microsoft Docs"
 ms.custom: ""
-ms.date: "08/14/2018"
+ms.date: "03/21/2019"
 ms.service: sql-database
 ms.reviewer: ""
 ms.topic: "language-reference"
@@ -32,7 +32,7 @@ monikerRange: "= azuresqldb-current || = sqlallproducts-allversions"
 |avg_cpu_percent|**decimal (5,2)**|Average compute utilization in percentage of the limit of the service tier.|  
 |avg_data_io_percent|**decimal (5,2)**|Average data I/O utilization in percentage of the limit of the service tier.|  
 |avg_log_write_percent|**decimal (5,2)**|Average write I/O throughput utilization as percentage of the limit of the service tier.|  
-|avg_memory_usage_percent|**decimal (5,2)**|Average memory utilization in percentage of the limit of the service tier.<br /><br /> This includes memory used for storage of In-Memory OLTP objects.|  
+|avg_memory_usage_percent|**decimal (5,2)**|Average memory utilization in percentage of the limit of the service tier.<br /><br /> This includes memory used for  buffer pool pages and storage of In-Memory OLTP objects.|  
 |xtp_storage_percent|**decimal (5,2)**|Storage utilization for In-Memory OLTP in percentage of the limit of the service tier (at the end of the reporting interval). This includes memory used for storage of the following In-Memory OLTP objects: memory-optimized tables, indexes, and table variables. It also includes memory used for processing ALTER TABLE operations.<br /><br /> Returns 0 if In-Memory OLTP is not used in the database.|  
 |max_worker_percent|**decimal (5,2)**|Maximum concurrent workers (requests) in percentage of the limit of the database's service tier.|  
 |max_session_percent|**decimal (5,2)**|Maximum concurrent sessions in percentage of the limit of the database's service tier.|  

docs/relational-databases/system-dynamic-management-views/sys-dm-db-resource-stats-azure-sql-database.md

@@ -27,10 +27,6 @@ monikerRange: "= azuresqldb-mi-current || >= sql-server-2016 || = sqlallproducts
 
 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent allows you to use tokens in [!INCLUDE[tsql](../../includes/tsql-md.md)] job step scripts. Using tokens when you write your job steps gives you the same flexibility that variables provide when you write software programs. After you insert a token in a job step script, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent replaces the token at run time, before the job step is executed by the [!INCLUDE[tsql](../../includes/tsql-md.md)] subsystem.  
 
-> [!IMPORTANT]
-> Starting with [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] Service Pack 1, the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent job step token syntax changed. As a result, an escape macro must now accompany all tokens used in job steps, or else those job steps will fail. Using escape macros and updating your [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent job steps that use tokens are described in the following sections, "Understanding Using Tokens," " [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent Tokens and Macros," and "Updating Job Steps to Use Macros." In addition, the [!INCLUDE[ssVersion2000](../../includes/ssversion2000-md.md)] syntax, which used square brackets to call out [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent job step tokens (for example, "`[DATE]`") has also changed. You must now enclose token names in parentheses and place a dollar sign (`$`) at the beginning of the token syntax. For example:  
-> 
-> `$(ESCAPE_`*macro name*`(DATE))`  
 
 ## Understanding Using Tokens  
 
@@ -95,10 +91,6 @@ The following tables list and describe the tokens and macros that [!INCLUDE[ssNo
 |**$(ESCAPE_NONE(**_token\_name_**))**|Replaces token without escaping any characters in the string. This macro is provided to support backward compatibility in environments where token replacement strings are only expected from trusted users. For more information, see "Updating Job Steps to Use Macros," later in this topic.|  
 
 ## Updating Job Steps to Use Macros  
-Beginning with [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] Service Pack 1, job steps that contain tokens without escape macros will fail and return an error message indicating the job step contains one or more tokens that must be updated with a macro before the job can run.  
-  
-A script is provided with [!INCLUDE[msCoName](../../includes/msconame_md.md)] Knowledge Base article 915845: [SQL Server Agent Job Steps That Use Tokens Fail in SQL Server 2005 Service Pack 1](https://support.microsoft.com/kb/915845).You can use this script to update all of your job steps that use tokens with the **ESCAPE_NONE** macro. After using this script, we recommend that you review your job steps that use tokens as soon as possible, and replace the **ESCAPE_NONE** macro with an escape macro that is appropriate for the job step context.  
-  
 The following table describes how token replacement is handled by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent. To turn alert token replacement on or off, right-click **SQL Server Agent** in Object Explorer, select **Properties**, and on the **Alert System** page, select or clear the **Replace tokens for all job responses to alerts** check box.  
 
 |Token syntax|Alert token replacement on|Alert token replacement off|  

docs/sql-server/install/work-with-multiple-versions-and-instances-of-sql-server.md

@@ -48,14 +48,14 @@ RAND ( [ seed ] )
 
  For one connection, if RAND() is called with a specified seed value, all subsequent calls of RAND() produce results based on the seeded RAND() call. For example, the following query will always return the same sequence of numbers.  
 
-```  
+```sql  
 SELECT RAND(100), RAND(), RAND()   
 ```  
 
 ## Examples  
  The following example produces four different random numbers that are generated by the RAND function.  
 
-```  
+```sql  
 DECLARE @counter smallint;  
 SET @counter = 1;  
 WHILE @counter < 5