Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into release-remove-sscurrent-tag

Author: v-alje

docs/relational-databases/security/sql-vulnerability-assessment.md

@@ -1,47 +1,51 @@
 ---
-title: "SQL Vulnerability Assessment | Microsoft Docs"
-description: Use the SQL Vulnerability Assessment tool to help discover, track, and remediate potential database vulnerabilities in SQL Server.
+title: "Vulnerability assessment for SQL Server"
+description: Use the vulnerability assessment scanner to discover, track, and remediate potential database vulnerabilities in SQL Server.
 ms.custom: ""
-ms.date: "11/30/2017"
+ms.date: "04/26/2021"
 ms.prod: sql
 ms.prod_service: "security, sql-database"
-ms.reviewer: ""
 ms.technology: security
 ms.topic: conceptual
 helpviewer_keywords: 
   - "SQL Vulnerability Assessment"
-author: yualan
-ms.author: alayu
-monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
+author: davidtrigano
+ms.author: datrigan
+monikerRange: ">=sql-server-2016"
 ---
-# SQL Vulnerability Assessment
+# Vulnerability assessment for SQL Server
 
-[!INCLUDE [SQL Server Azure SQL Database](../../includes/applies-to-version/sql-asdb.md)]
+[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-SQL Vulnerability Assessment is an easy to use tool that can help you discover, track, and remediate potential database vulnerabilities. Use it to proactively improve your database security.
+SQL vulnerability assessment is an easy to use tool that can help you discover, track, and remediate potential database vulnerabilities. Use it to proactively improve your database security.
 
-Vulnerability Assessment is **supported for SQL Server 2012 and later**, and can also be run on [Azure SQL Database](/azure/sql-database/sql-vulnerability-assessment).
+The vulnerability assessment tool is available in [SQL Server Management Studio (SSMS)](../../ssms/download-sql-server-management-studio-ssms.md) for SQL Server 2012 or later.
 
-## Vulnerability Assessment features
-SQL Vulnerability Assessment (VA) is a service that provides visibility into your security state, and includes actionable steps to resolve security issues and enhance your database security. It can help you:
-- Meet compliance requirements that require database scan reports. 
-- Meet data privacy standards.
-- Monitor a dynamic database environment where changes are difficult to track.
+  > [!TIP]   
+  > For a comprehensive solution with advanced threat protection capabilities, use [Azure Defender for SQL Servers on machines](https://docs.microsoft.com/azure/security-center/defender-for-sql-introduction). To use Azure Defender, your SQL Server must be connected to Azure.
+  > 
+  >  For Azure SQL Database, Azure Synapse Analytics, and SQL Managed Instance, use [Azure Defender for SQL Database](https://docs.microsoft.com/azure/security-center/defender-for-sql-introduction).
+
+## Vulnerability assessment features
+SQL vulnerability assessment (VA) is a service that provides visibility into your security state, and includes actionable steps to resolve security issues and enhance your database security. It can help you:
+- Meet compliance requirements that require database scan reports
+- Meet data privacy standards
+- Monitor a dynamic database environment where changes are difficult to track
 
 The VA service runs a scan directly on your database. The service employs a knowledge base of rules that flag security vulnerabilities and highlight deviations from best practices, such as misconfigurations, excessive permissions, and unprotected sensitive data. The rules are based on Microsoft's recommended best practices, and focus on the security issues that present the biggest risks to your database and its valuable data. These rules also represent many of the requirements from various regulatory bodies to meet their compliance standards.
 
 Results of the scan include actionable steps to resolve each issue and provide customized remediation scripts where applicable. An assessment report can be customized for your environment, by setting an acceptable baseline for permission configurations, feature configurations and database settings. 
 
 ## Prerequisites
-This feature is only available on SQL Server Management Studio (SSMS) v17.4 or later. Please make sure you are using the latest version. You can find the latest version [here](../../ssms/download-sql-server-management-studio-ssms.md).
+This feature is only available on SQL Server Management Studio (SSMS) v17.4 or later. You can find the latest version [here](../../ssms/download-sql-server-management-studio-ssms.md).
 
 ## Getting started
-To get started with running a Vulnerability Assessment on your database, follow these steps:
+To run a vulnerability scan on your database, follow these steps:
    1.	Open **SQL Server Management Studio**.
 
    2.	Connect to an instance of the SQL Server Database Engine or localhost.
 
-   3.	Expand **Databases**, right-click a database, point to **Tasks**, select **Vulnerability Assessment**, and click on **Scan for Vulnerabilities...**
+   3.	Expand **Databases**, right-click a database, point to **Tasks**, select **Vulnerability assessment**, and select **Scan for Vulnerabilities...**
 
    4.	You can run a scan that checks for server-level issues by scanning one of the system databases. Expand **System Databases**, right-click the **master** database, point to **Tasks**, select **Vulnerability Assessment**, and click on **Scan for Vulnerabilities...**
 
@@ -52,9 +56,9 @@ Use the following steps to run and manage vulnerability assessments on your data
 
 ### 1. Run a scan
 
-The Scan For Vulnerabilities dialog allows you to specify the location where scans will be saved. You can leave the default location or click **Browse...** to save the scan results to a different location.
+The **Scan For Vulnerabilities** dialog allows you to specify the location where scans will be saved. You can leave the default location or click **Browse...** to save the scan results to a different location.
 
-When you are ready to scan, click **OK** to scan your database for vulnerabilities.
+When you are ready to scan, select **OK** to scan your database for vulnerabilities.
 
   > [!NOTE]   
   > The scan is lightweight and safe. It takes a few seconds to run, and is entirely read-only. It does not make any changes to your database.
@@ -89,21 +93,21 @@ After you complete setting up your **Rule Baselines**, run a new scan to view th
 
 ### 6. Open a previously run scan
 
-You can view the results of previously run Vulnerability Assessments at any time by opening an existing scan. Do so by right-clicking a database, pointing to **Tasks**, selecting **Vulnerability Assessment**, and clicking on **Open Existing Scan...**  Select the scan results file you would like to view and click **Open**. 
+You can view the results of previously run vulnerability assessments at any time by opening an existing scan. Do so by right-clicking a database, pointing to **Tasks**, selecting **Vulnerability Assessment**, and selecting **Open Existing Scan...**. Select the scan results file you would like to view and select **Open**. 
 
 You can also open an existing scan result via the **File->Open** menu. Select **Vulnerability Assessment...** and open the **scans** directory to find the scan result you wish to view.
 
 ![open existing scan](media/sql-vulnerability-assessment/7-ssmsopenexistingscan.png)
 
 VA can now be used to monitor that your databases maintain a high level of security at all times, and that your organizational policies are met. If compliance reports are required, VA reports can be helpful to facilitate the compliance process.
 
-## Manage Vulnerability Assessments using PowerShell
-You can use PowerShell cmdlets to programmatically manage Vulnerability Assessments for your SQL Servers. The cmdlets can be used to run assessments programmatically, export the results and manage baselines.
+## Manage vulnerability assessments using PowerShell
+You can use PowerShell cmdlets to programmatically manage vulnerability assessments for your SQL Servers. The cmdlets can be used to run assessments programmatically, export the results and manage baselines.
 To get started, download the latest [SqlServer PowerShell module](https://www.powershellgallery.com/packages/SqlServer/) from the PowerShell Gallery site. You can learn more [here](/archive/blogs/sqlsecurity/powershell-cmdlets-for-managing-sql-vulnerability-assessments).
 
 ## Next steps
-Learn more about SQL Vulnerability Assessment using the following resources:
-- [Running a Vulnerability Assessment on Azure SQL Database](/azure/sql-database/sql-vulnerability-assessment) 
-- [Channel 9 video demonstrating the use of Vulnerability Assessment](https://channel9.msdn.com/Shows/Data-Exposed/Track-and-remediate-potential-database-vulnerabilities-with-SQL-Vulnerability-Assessment)
+Learn more about SQL vulnerability assessment using the following resources:
+- [Running a vulnerability assessment scan on Azure SQL Database](/azure/sql-database/sql-vulnerability-assessment) 
+- [Channel 9 video demonstrating the use of vulnerability assessments](https://channel9.msdn.com/Shows/Data-Exposed/Track-and-remediate-potential-database-vulnerabilities-with-SQL-Vulnerability-Assessment)
 
 

docs/relational-databases/system-catalog-views/sys-database-scoped-credentials-transact-sql.md

@@ -25,17 +25,31 @@ monikerRange: "=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sq
 
   Returns one row for each database scoped credential in the database.  
 
+::: moniker range="=sql-server-2016"
 |Column name|Data type|Description|  
 |-----------------|---------------|-----------------|  
 |name|**sysname**|Name of the database scoped credential. Is unique in the database.|  
 |credential_id|**int**|ID of the database scoped credential. Is unique in the database.|  
-|principal_id|**int**|ID of the database principal who owns the key.|  
 |credential_identity|**nvarchar(4000)**|Name of the identity to use. This will generally be a Windows user. It does not have to be unique.|  
 |create_date|**datetime**|Time at which the database scoped credential was created.|  
 |modify_date|**datetime**|Time at which the database scoped credential was last modified.|  
 |target_type|**nvarchar(100)**|Type of database scoped credential. Returns `NULL` for database scoped credentials.|  
 |target_id|**int**|ID of the object that the database scoped credential is mapped to. Returns 0 for database scoped credentials|  
+::: moniker-end
 
+::: moniker range=">=sql-server-2017||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-linux-2017||=azuresqldb-mi-current"
+|Column name|Data type|Description|  
+|-----------------|---------------|-----------------|  
+|name|**sysname**|Name of the database scoped credential. Is unique in the database.|  
+|credential_id|**int**|ID of the database scoped credential. Is unique in the database.|  
+|principal_id|**int**|ID of the database principal who owns the key.|  
+|credential_identity|**nvarchar(4000)**|Name of the identity to use. This will generally be a Windows user. It does not have to be unique.|  
+|create_date|**datetime**|Time at which the database scoped credential was created.|  
+|modify_date|**datetime**|Time at which the database scoped credential was last modified.|  
+|target_type|**nvarchar(100)**|Type of database scoped credential. Returns `NULL` for database scoped credentials.|  
+|target_id|**int**|ID of the object that the database scoped credential is mapped to. Returns 0 for database scoped credentials|  
+::: moniker-end
+
 ## Permissions  
  Requires `CONTROL` permission on the database.  
 

docs/relational-databases/system-functions/sys-fn-my-permissions-transact-sql.md

@@ -76,7 +76,11 @@ GO
 ```  
 
  If DEFAULT is supplied as the value of *securable* or *securable_class*, the value will be interpreted as NULL.  
-  
+ 
+   
+## Permissions  
+ Requires membership in the public role.  
+ 
 ## Examples  
 
 ### A. Listing effective permissions on the server  

docs/ssdt/download-sql-server-data-tools-ssdt.md

@@ -88,10 +88,10 @@ The installer lists available Visual Studio instances to add SSDT tools. If Visu
 
 ## SSDT for VS 2017 (standalone installer)
 
-:::image type="icon" source="media/download.png" border="false"::: **[Download SSDT for Visual Studio 2017 (15.9.7)](https://go.microsoft.com/fwlink/?linkid=2151759)**
+:::image type="icon" source="media/download.png" border="false"::: **[Download SSDT for Visual Studio 2017 (15.9.8)](https://go.microsoft.com/fwlink/?linkid=2161172)**
 
 > [!IMPORTANT]
-> * Before installing SSDT for Visual Studio 2017 (15.9.7), uninstall *Analysis Services Projects* and *Reporting Services Projects* extensions if they are already installed, and close all VS instances. 
+> * Before installing SSDT for Visual Studio 2017 (15.9.8), uninstall *Analysis Services Projects* and *Reporting Services Projects* extensions if they are already installed, and close all VS instances. 
 > * Removed the inbox component Power Query Source for SQL Server 2017. Now we have announced Power Query Source for SQL Server 2017 & 2019 as out-of-box component, which can be downloaded [here](https://www.microsoft.com/download/details.aspx?id=100619).
 > * To design packages using Oracle and Teradata connectors and targeting an earlier version of SQL Server prior to SQL 2019, in addition to the [Microsoft Oracle Connector for SQL 2019](https://www.microsoft.com/download/details.aspx?id=58228) and [Microsoft Teradata Connector for SQL 2019](https://www.microsoft.com/download/details.aspx?id=100599), you need to also install the corresponding version of Microsoft Connector for Oracle and Teradata by Attunity.
 >    * [Microsoft Connector Version 5.0 for Oracle and Teradata by Attunity targeting SQL Server 2017](https://www.microsoft.com/download/details.aspx?id=55179)
@@ -111,17 +111,17 @@ SSDT for Visual Studio 2017 has the same [system requirements](/visualstudio/pro
 
 This release of **SSDT for VS 2017** can be installed in the following languages:
 
-* [Chinese (Simplified)](https://go.microsoft.com/fwlink/?linkid=2151759&clcid=0x804)
-* [Chinese (Traditional)](https://go.microsoft.com/fwlink/?linkid=2151759&clcid=0x404)
-* [English (United States)](https://go.microsoft.com/fwlink/?linkid=2151759&clcid=0x409)
-* [French](https://go.microsoft.com/fwlink/?linkid=2151759&clcid=0x40c)
-* [German](https://go.microsoft.com/fwlink/?linkid=2151759&clcid=0x407)
-* [Italian](https://go.microsoft.com/fwlink/?linkid=2151759&clcid=0x410)
-* [Japanese](https://go.microsoft.com/fwlink/?linkid=2151759&clcid=0x411)
-* [Korean](https://go.microsoft.com/fwlink/?linkid=2151759&clcid=0x412)
-* [Portuguese (Brazil)](https://go.microsoft.com/fwlink/?linkid=2151759&clcid=0x416)
-* [Russian](https://go.microsoft.com/fwlink/?linkid=2151759&clcid=0x419)
-* [Spanish](https://go.microsoft.com/fwlink/?linkid=2151759&clcid=0x40a)
+* [Chinese (Simplified)](https://go.microsoft.com/fwlink/?linkid=2161172&clcid=0x804)
+* [Chinese (Traditional)](https://go.microsoft.com/fwlink/?linkid=2161172&clcid=0x404)
+* [English (United States)](https://go.microsoft.com/fwlink/?linkid=2161172&clcid=0x409)
+* [French](https://go.microsoft.com/fwlink/?linkid=2161172&clcid=0x40c)
+* [German](https://go.microsoft.com/fwlink/?linkid=2161172&clcid=0x407)
+* [Italian](https://go.microsoft.com/fwlink/?linkid=2161172&clcid=0x410)
+* [Japanese](https://go.microsoft.com/fwlink/?linkid=2161172&clcid=0x411)
+* [Korean](https://go.microsoft.com/fwlink/?linkid=2161172&clcid=0x412)
+* [Portuguese (Brazil)](https://go.microsoft.com/fwlink/?linkid=2161172&clcid=0x416)
+* [Russian](https://go.microsoft.com/fwlink/?linkid=2161172&clcid=0x419)
+* [Spanish](https://go.microsoft.com/fwlink/?linkid=2161172&clcid=0x40a)
 
 ### Considerations and limitations
 

docs/ssdt/release-notes-ssdt.md

@@ -40,6 +40,30 @@ GeneMi , 2019/03/22.
 P.S.  there's no need to keep this large HTML comment indefinitely.
 -->
 
+## 15.9.8,  SSDT for VS 2017
+
+_Released:_   Apr 27, 2021  
+_Build Number:_   14.0.16236.0  
+_SSDT for Visual Studio 2017._
+
+### What's New?
+
+| New Item | Details |
+|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Integration Services (SSIS) | Add ExecuteOnProxy property on Execute SQL Task and Execute Process Task so as to support [enabling self-hosted Integration Runtime as proxy](https://docs.microsoft.com/azure/data-factory/self-hosted-integration-runtime-proxy-ssis). |
+| Integration Services (SSIS) | Allow connectivity retry for OLE DB connection manager via exposing ConnectRetryCount and ConnectRetryInterval properties. |
+| Integration Services (SSIS) | List available locations based on selected subscription in Integration Runtime Creation Wizard. |
+| Integration Services (SSIS) | Fixed an issue that test connection on Analysis Services connection manager may fail due to fail to load managed ADAL component. |
+| Integration Services (SSIS) | Fixed some issues related to accessibility and high DPI. |
+
+### Known issues
+
+| Known issue | Details |
+| :---------- | :------ |
+| SSIS Execute Package Task doesn't support debugging when ExecuteOutOfProcess is set to True. | This issue applies only to debugging. Save, deploy, and execution via DTExec.exe or SSIS catalog isn't affected. |
+|   |   |
+
+
 ## 15.9.7,  SSDT for VS 2017
 
 _Released:_   Jan 5, 2021  

docs/t-sql/functions/objectproperty-transact-sql.md

@@ -161,6 +161,7 @@ OBJECTPROPERTY ( id , property )
 ## Exceptions  
  Returns NULL on error or if a caller does not have permission to view the object.  
 
+## Permissions 
  A user can only view the metadata of securables that the user owns or on which the user has been granted permission. This means that metadata-emitting, built-in functions such as OBJECTPROPERTY may return NULL if the user does not have any permission on the object. For more information, see [Metadata Visibility Configuration](../../relational-databases/security/metadata-visibility-configuration.md).  
 
 ## Remarks  

docs/tools/configuration-manager/connecting-using-ipv6.md

@@ -18,7 +18,7 @@ ms.author: maghan
 monikerRange: ">=sql-server-2016"
 ---
 # Connecting Using IPv6
-[!INCLUDE [SQL Server Windows Only - ASDBMI ](../../includes/applies-to-version/sql-windows-only-asdbmi.md)]
+[!INCLUDE [SQL Server Windows Only](../../includes/applies-to-version/sql-windows-only.md)]
   [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Native Client fully support both Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). When Windows is configured with IPv6 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], components automatically recognize the existence of IPv6. No special [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] configuration is necessary.  
 
  Support includes but is not limited to the following: