More fix of 1552923. Metadata validation errors. Adding 'author: VanMSFT'.

Author: MightyPen

.openpublishing.redirection.json

@@ -3632,7 +3632,12 @@
             "redirect_url":"/sql/tools/sql-server-profiler/start-sql-server-profiler",
             "redirect_document_id":false
         },
-                {
+        {
+            "source_path": "docs/relational-databases/system-stored-procedures/sp-dropalias-transact-sql.md",
+            "redirect_url": "/sql/relational-databases/system-stored-procedures/",
+            "redirect_document_id": false
+        },
+        {
             "source_path": "docs/relational-databases/system-dynamic-management-views/linux-process-dynamic-management-views-transact-sql.md",
             "redirect_url": "/sql/relational-databases/system-dynamic-management-views/system-dynamic-management-views",
             "redirect_document_id": false

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

@@ -14,10 +14,11 @@ helpviewer_keywords:
   - "sp_dropanonymousagent"
 ms.assetid: 4cb96efa-9358-44a3-a8ee-a7e181bed089
 ms.author: vanto
-manager: craigg
-manager: craigg
+author: VanMSFT
+manager: jroth
 ---
 # sp_dropanonymousagent (Transact-SQL)
+
 [!INCLUDE[tsql-appliesto-ss2008-xxxx-xxxx-xxx-md](../../includes/tsql-appliesto-ss2008-xxxx-xxxx-xxx-md.md)]
 
   Drops an anonymous agent for replication monitoring at the distributor from the Publisher. This stored procedure is executed at the Publisher on any database.  
@@ -27,7 +28,6 @@ manager: craigg
 ## Syntax  
 
 ```  
-  
 sp_dropanonymousagent [ @subid= ] sub_id    , [ @type= ] type  
 ```  
 

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

@@ -16,10 +16,11 @@ helpviewer_keywords:
   - "sp_dropapprole"
 ms.assetid: ea1aefe6-8f7d-46e9-a3cb-7b037b393e73
 ms.author: vanto
-manager: craigg
-manager: craigg
+author: VanMSFT
+manager: jroth
 ---
 # sp_dropapprole (Transact-SQL)
+
 [!INCLUDE[tsql-appliesto-ss2008-xxxx-xxxx-xxx-md](../../includes/tsql-appliesto-ss2008-xxxx-xxxx-xxx-md.md)]
 
   Removes an application role from the current database.  
@@ -32,7 +33,6 @@ manager: craigg
 ## Syntax  
 
 ```  
-  
 sp_dropapprole [@rolename = ] 'role'  
 ```  
 
@@ -54,7 +54,7 @@ sp_dropapprole [@rolename = ] 'role'
 ## Examples  
  The following example removes the `SalesApp` application role from the current database.  
 
-```  
+```sql
 EXEC sp_dropapprole 'SalesApp';  
 ```  
 

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

@@ -16,10 +16,11 @@ helpviewer_keywords:
   - "sp_dropremotelogin"
 ms.assetid: 9f097652-a286-40b2-be73-568d77ada698
 ms.author: vanto
-manager: craigg
-manager: craigg
+author: VanMSFT
+manager: jroth
 ---
 # sp_dropremotelogin (Transact-SQL)
+
 [!INCLUDE[tsql-appliesto-ss2008-xxxx-xxxx-xxx-md](../../includes/tsql-appliesto-ss2008-xxxx-xxxx-xxx-md.md)]
 
   Removes a remote login mapped to a local login used to execute remote stored procedures against the local server running [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].  
@@ -32,7 +33,6 @@ manager: craigg
 ## Syntax  
 
 ```  
-  
 sp_dropremotelogin [ @remoteserver = ] 'remoteserver'   
      [ , [ @loginame = ] 'login' ]   
      [ , [ @remotename = ] 'remote_name' ]  
@@ -68,21 +68,21 @@ sp_dropremotelogin [ @remoteserver = ] 'remoteserver'
 ### A. Dropping all remote logins for a remote server  
  The following example removes the entry for the remote server `ACCOUNTS`, and, therefore, removes all mappings between logins on the local server and remote logins on the remote server.  
 
-```  
+```sql
 EXEC sp_dropremotelogin 'ACCOUNTS';  
 ```  
 
 ### B. Dropping a login mapping  
  The following example removes the entry for mapping remote logins from the remote server `ACCOUNTS` to the local login `Albert`.  
 
-```  
+```sql
 EXEC sp_dropremotelogin 'ACCOUNTS', 'Albert';  
 ```  
 
 ### C. Dropping a remote user  
  The following example removes the login for the remote login `Chris` on the remote server `ACCOUNTS` that was mapped to the local login `salesmgr`.  
 
-```  
+```sql
 EXEC sp_dropremotelogin 'ACCOUNTS', 'salesmgr', 'Chris';  
 ```  
 

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

@@ -16,11 +16,12 @@ helpviewer_keywords:
   - "sp_droprolemember"
 ms.assetid: c2f19ab1-e742-4d56-ba8e-8ffd40cf4925
 ms.author: vanto
-manager: craigg
-manager: craigg
+author: VanMSFT
+manager: jroth
 monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
 # sp_droprolemember (Transact-SQL)
+
 [!INCLUDE[tsql-appliesto-ss2008-all-md](../../includes/tsql-appliesto-ss2008-all-md.md)]
 
   Removes a security account from a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] role in the current database.  
@@ -31,17 +32,17 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
  ![Topic link icon](../../database-engine/configure-windows/media/topic-link.gif "Topic link icon") [Transact-SQL Syntax Conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)  
 
 ## Syntax  
-  
+
+### Syntax for both SQL Server and Azure SQL Database
+
 ```  
--- Syntax for SQL Server and Azure SQL Database  
-  
 sp_droprolemember [ @rolename = ] 'role' ,   
      [ @membername = ] 'security_account'  
 ```  
-  
+
+### Syntax for both Azure SQL Data Warehouse and Parallel Data Warehouse
+
 ```  
--- Syntax for Azure SQL Data Warehouse and Parallel Data Warehouse  
-  
 sp_droprolemember 'role' ,  
      'security_account'  
 ```  
@@ -69,14 +70,14 @@ sp_droprolemember 'role' ,
 ## Examples  
  The following example removes the user `JonB` from the role `Sales`.  
 
-```  
+```sql
 EXEC sp_droprolemember 'Sales', 'Jonb';  
 ```  
 
 ## Examples: [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)] and [!INCLUDE[ssPDW](../../includes/sspdw-md.md)]  
  The following example removes the user `JonB` from the role `Sales`.  
 
-```  
+```sql
 EXEC sp_droprolemember 'Sales', 'JonB'  
 ```  
 

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

@@ -16,10 +16,11 @@ helpviewer_keywords:
   - "sp_enum_login_for_proxy"
 ms.assetid: 62a75019-248a-44c8-a5cc-c79f55ea3acf
 ms.author: vanto
-manager: craigg
-manager: craigg
+author: VanMSFT
+manager: jroth
 ---
 # sp_enum_login_for_proxy (Transact-SQL)
+
 [!INCLUDE[tsql-appliesto-ss2008-xxxx-xxxx-xxx-md](../../includes/tsql-appliesto-ss2008-xxxx-xxxx-xxx-md.md)]
 
   Lists associations between security principals and proxies.  
@@ -29,7 +30,6 @@ manager: craigg
 ## Syntax  
 
 ```  
-  
 sp_enum_login_for_proxy  
     [ @name = ] 'name'  
     [ @proxy_id = ] id,  
@@ -57,6 +57,7 @@ sp_enum_login_for_proxy
 |**proxy_name**|**sysname**|The name of the proxy.|  
 |**name**|**sysname**|Name of the security principal for the association.|  
 |**flags**|**int**|Type of the security principal.<br /><br /> **0** = [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] login<br /><br /> **1** = Fixed system role<br /><br /> **2** = Database role in **msdb**|  
+| &nbsp; | &nbsp; | &nbsp; |
 
 ## Remarks  
  When no parameters are provided, **sp_enum_login_for_proxy** lists information about all logins in the instance for every proxy.  
@@ -75,7 +76,7 @@ sp_enum_login_for_proxy
 ### A. Listing all associations  
  The following example lists all permissions established between logins and proxies in the current instance.  
 
-```  
+```sql
 USE msdb ;  
 GO  
 
@@ -86,7 +87,7 @@ GO
 ### B. Listing proxies for a specific login  
  The following example lists the proxies that the login `terrid` has access to.  
 
-```  
+```sql
 USE msdb ;  
 GO  
 

docs/relational-databases/system-stored-procedures/sp-enum-login-for-proxy-transact-sql.md

@@ -16,10 +16,11 @@ helpviewer_keywords:
   - "sp_enum_proxy_for_subsystems"
 ms.assetid: 580cc3be-1068-4a96-8d15-78ca3a5bb719
 ms.author: vanto
-manager: craigg
+author: VanMSFT
 manager: craigg
 ---
 # sp_enum_proxy_for_subsystem (Transact-SQL)
+
 [!INCLUDE[tsql-appliesto-ss2008-xxxx-xxxx-xxx-md](../../includes/tsql-appliesto-ss2008-xxxx-xxxx-xxx-md.md)]
 
   Lists permissions for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent proxies to access subsystems.  
@@ -29,7 +30,6 @@ manager: craigg
 ## Syntax  
 
 ```  
-  
 sp_enum_proxy_for_subsystem  
     [ @proxy_id = ] proxy_id,  
     [ @proxy_name = ] 'proxy_name',  
@@ -61,6 +61,7 @@ sp_enum_proxy_for_subsystem
 |**subsystem_name**|**sysname**|The name of the subsystem.|  
 |**proxy_id**|**int**|Proxy identification number.|  
 |**proxy_name**|**sysname**|The name of the proxy.|  
+|   |   |   |
 
 ## Remarks  
  When no parameters are provided, **sp_enum_proxy_for_subsystem** lists information about all proxies in the instance for every subsystem.  
@@ -79,7 +80,7 @@ sp_enum_proxy_for_subsystem
 ### A. Listing all associations  
  The following example lists all permissions established between proxies and subsystems for the current instance.  
 
-```  
+```sql
 USE msdb ;  
 GO  
 
@@ -90,7 +91,7 @@ GO
 ### B. Determining if a proxy has access to a specific subsystem  
  The following example returns a row if the proxy `Catalog application proxy` has access to the `ActiveScripting` subsystem. Otherwise, the example returns an empty result set.  
 
-```  
+```sql
 USE msdb ;  
 GO  
 

docs/relational-databases/system-stored-procedures/sp-enum-proxy-for-subsystem-transact-sql.md

@@ -16,10 +16,11 @@ helpviewer_keywords:
   - "sp_grant_login_to_proxy"
 ms.assetid: 90e1a6d5-a692-4462-a163-4b0709d83150
 ms.author: vanto
-manager: craigg
-manager: craigg
+author: VanMSFT
+manager: jrothj
 ---
 # sp_grant_login_to_proxy (Transact-SQL)
+
 [!INCLUDE[tsql-appliesto-ss2008-xxxx-xxxx-xxx-md](../../includes/tsql-appliesto-ss2008-xxxx-xxxx-xxx-md.md)]
 
   Grants a security principal access to a proxy.  
@@ -30,7 +31,6 @@ manager: craigg
 ## Syntax  
 
 ```  
-  
 sp_grant_login_to_proxy   
      { [ @login_name = ] 'login_name'   
      | [ @fixed_server_role = ] 'fixed_server_role'   
@@ -66,7 +66,7 @@ sp_grant_login_to_proxy
 ## Examples  
  The following example allows the login `adventure-works\terrid` to use the proxy `Catalog application proxy`.  
 
-```  
+```sql
 USE msdb ;  
 GO  
 

docs/relational-databases/system-stored-procedures/sp-grant-login-to-proxy-transact-sql.md

@@ -15,11 +15,12 @@ dev_langs:
 helpviewer_keywords: 
   - "sp_grant_proxy_to_subsystem"
 ms.assetid: 866aaa27-a1e0-453a-9b1b-af39431ad9c2
+author: VanMSFT
 ms.author: vanto
-manager: craigg
-manager: craigg
+manager: jroth
 ---
 # sp_grant_proxy_to_subsystem (Transact-SQL)
+
 [!INCLUDE[tsql-appliesto-ss2008-xxxx-xxxx-xxx-md](../../includes/tsql-appliesto-ss2008-xxxx-xxxx-xxx-md.md)]
 
   Grants a proxy access to a subsystem.  
@@ -29,7 +30,6 @@ manager: craigg
 ## Syntax  
 
 ```  
-  
 sp_grant_proxy_to_subsystem  
      { [ @proxy_id = ] proxy_id | [ @proxy_name = ] 'proxy_name' },  
      { [ @subsystem_id = ] subsystem_id | [ @subsystem_name = ] 'subsystem_name' }  
@@ -58,6 +58,7 @@ sp_grant_proxy_to_subsystem
 |**10**|Analysis Services Command|  
 |**11**|[!INCLUDE[ssIS](../../includes/ssis-md.md)] package execution|  
 |**12**|PowerShell Script|  
+|   |   |
 
 `[ @subsystem_name = ] 'subsystem_name'`
  The name of the subsystem to grant access to. The **subsystem_name** is **sysname**, with a default of NULL. Either *subsystem_id* or *subsystem_name* must be specified, but both cannot be specified. The following table lists the values for each subsystem.  
@@ -75,6 +76,7 @@ sp_grant_proxy_to_subsystem
 |**ANALYSISCOMMAND**|Analysis Services Command|  
 |**Dts**|SSIS package execution|  
 |**PowerShell**|PowerShell Script|  
+|   |   |
 
 ## Remarks  
  Granting a proxy access to a subsystem does not change the permissions for the principal specified in the proxy.  
@@ -87,7 +89,7 @@ sp_grant_proxy_to_subsystem
 ### A. Granting access to a subsystem by ID  
  The following example grants the proxy `Catalog application proxy` access to the ActiveX Scripting subsystem.  
 
-```  
+```sql
 USE msdb ;  
 GO  
 
@@ -100,7 +102,7 @@ GO
 ### B. Granting access to a subsystem by name.  
  The following example grants the proxy `Catalog application proxy` access to the SSIS package execution subsystem.  
 
-```  
+```sql
 USE msdb ;  
 GO