Merge pull request #178760 from linda33wj/purview

Add MySQL, PostgreSQL, Salesforce support in Purview

Author: PMEds28

articles/purview/media/register-scan-mysql/register-sources.png

@@ -10,7 +10,7 @@ ms.date: 11/02/2021
 ms.custom: template-how-to, ignite-fall-2021
 ---
 
-# Connect to and manage Cassandra in Azure Purview
+# Connect to and manage Cassandra in Azure Purview (Preview)
 
 This article outlines how to register Cassandra, and how to authenticate and interact with Cassandra in Azure Purview. For more information about Azure Purview, read the [introductory article](overview.md).
 

articles/purview/media/register-scan-mysql/scan.png

@@ -10,7 +10,7 @@ ms.date: 11/02/2021
 ms.custom: template-how-to, ignite-fall-2021
 ---
 
-# Connect to and manage Google BigQuery projects in Azure Purview
+# Connect to and manage Google BigQuery projects in Azure Purview (Preview)
 
 This article outlines how to register Google BigQuery projects, and how to authenticate and interact with Google BigQuery in Azure Purview. For more information about Azure Purview, read the [introductory article](overview.md).
 

articles/purview/media/register-scan-postgresql/register-sources.png

@@ -10,7 +10,7 @@ ms.date: 11/02/2021
 ms.custom: template-how-to, ignite-fall-2021
 ---
 
-# Connect to and manage Looker in Azure Purview
+# Connect to and manage Looker in Azure Purview (Preview)
 
 This article outlines how to register Looker, and how to authenticate and interact with Looker in Azure Purview. For more information about Azure Purview, read the [introductory article](overview.md).
 

articles/purview/media/register-scan-postgresql/scan.png

@@ -0,0 +1,145 @@
+---
+title: Connect to and manage MySQL
+description: This guide describes how to connect to MySQL in Azure Purview, and use Purview's features to scan and manage your MySQL source.
+author: linda33wj
+ms.author: jingwang
+ms.service: purview
+ms.subservice: purview-data-map
+ms.topic: how-to #Required; leave this attribute/value as-is.
+ms.date: 11/02/2021
+ms.custom: template-how-to #Required; leave this attribute/value as-is.
+---
+
+# Connect to and manage MySQL in Azure Purview (Preview)
+
+This article outlines how to register MySQL, and how to authenticate and interact with MySQL in Azure Purview. For more information about Azure Purview, read the [introductory article](overview.md).
+
+> [!IMPORTANT]
+> MySQL as a source is currently in PREVIEW. The [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+
+## Supported capabilities
+
+|**Metadata Extraction**|  **Full Scan**  |**Incremental Scan**|**Scoped Scan**|**Classification**|**Access Policy**|**Lineage**|
+|---|---|---|---|---|---|---|
+| [Yes](#register)| [Yes](#scan)| No | No | No | No| Yes|
+
+The supported MySQL server versions are 5.7 to 8.x.
+
+When scanning MySQL source, Purview supports:
+
+- Extracting metadata including MySQL server, databases, tables, views, table/view columns, etc.
+- Fetching lineage on assets relationships among tables and views.
+
+## Prerequisites
+
+* An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+
+* An active [Purview resource](create-catalog-portal.md).
+
+* You will need to be a Data Source Administrator and Data Reader to register a source and manage it in the Purview Studio. See [Azure Purview Permissions page](catalog-permissions.md) for details.
+
+* Set up the latest [self-hosted integration runtime](https://www.microsoft.com/download/details.aspx?id=39717). For more information, see [the create and configure a self-hosted integration runtime guide](../data-factory/create-self-hosted-integration-runtime.md).
+
+* Ensure [JDK 11](https://www.MySQL.com/java/technologies/javase-jdk11-downloads.html) is installed on the virtual machine where the self-hosted integration runtime is installed.
+
+* Ensure Visual C++ Redistributable for Visual Studio 2012 Update 4 is installed on the self-hosted integration runtime machine. If you don't have this update installed, [you can download it here](https://www.microsoft.com/download/details.aspx?id=30679).
+
+* The MySQL user must have the SELECT, SHOW VIEW and EXECUTE permissions for each target MySQL schema that contains metadata.
+
+## Register
+
+This section describes how to register MySQL in Azure Purview using the [Purview Studio](https://web.purview.azure.com/).
+
+### Steps to register
+
+To register a new MySQL source in your data catalog, do the following:
+
+1. Navigate to your Purview account in the [Purview Studio](https://web.purview.azure.com/resource/).
+1. Select **Data Map** on the left navigation.
+1. Select **Register**
+1. On Register sources, select **MySQL**. Select **Continue**.
+
+On the **Register sources (MySQL)** screen, do the following:
+
+1. Enter a **Name** that the data source will be listed within the Catalog.
+
+1. Enter the **Server** name to connect to a MySQL source. This can either be:
+    * A host name used to connect to the database server. For example: `MyDatabaseServer.com`
+    * An IP address. For example: `192.169.1.2`
+    * Its fully qualified JDBC connection string. For example:
+
+        ```
+        jdbc:mysql://COMPUTER_NAME_OR_IP/DATABASE_NAME
+        ```
+
+1. Enter the **Port** used to connect to the database server (3306 by default for MySQL).
+
+1. Select a collection or create a new one (Optional)
+
+1. Finish to register the data source.
+
+    :::image type="content" source="media/register-scan-mysql/register-sources.png" alt-text="register sources options" border="true":::
+
+## Scan
+
+Follow the steps below to scan MySQL to automatically identify assets and classify your data. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
+
+### Authentication for a scan
+
+The supported authentication type for a MySQL source is **Basic authentication**.
+
+### Create and run scan
+
+To create and run a new scan, do the following:
+
+1. In the Management Center, select Integration runtimes. Make sure a self-hosted integration runtime is set up. If it is not set up, use the steps mentioned [here](./manage-integration-runtimes.md) to create a self-hosted integration runtime.
+
+1. Navigate to **Sources**.
+
+1. Select the registered MySQL source.
+
+1. Select **+ New scan**.
+
+1. Provide the below details:
+
+    1. **Name**: The name of the scan
+
+    1. **Connect via integration runtime**: Select the configured self-hosted integration runtime
+
+    1. **Credential**: Select the credential to connect to your data source. Make sure to:
+        * Select **Basic Authentication** while creating a credential.
+        * Provide the user name used to connect to the database server in the User name input field.
+        * Store the user password used to connect to the database server in the secret key.
+
+    1. **Database**: List subset of schemas to import expressed as a semicolon separated list. For example, `schema1; schema2`. All user schemas are imported if that list is empty. All system schemas (for example, SysAdmin) and objects are ignored by default. When the list is empty, all available schemas are imported.
+
+        Acceptable schema name patterns using SQL LIKE expressions syntax include using %. For Example: `A%; %B; %C%; D`
+        * Start with A or
+        * End with B or
+        * Contain C or
+        * Equal D
+
+        Usage of NOT and special characters are not acceptable.
+
+    1. **Maximum memory available**: Maximum memory (in GB) available on customer's VM to be used by scanning processes. This is dependent on the size of MySQL source to be scanned.
+
+        > [!Note]
+        > As a thumb rule, please provide 1GB memory for every 1000 tables
+
+        :::image type="content" source="media/register-scan-mysql/scan.png" alt-text="scan MySQL" border="true":::
+
+1. Select **Continue**.
+
+1. Choose your **scan trigger**. You can set up a schedule or ran the scan once.
+
+1. Review your scan and select **Save and Run**.
+
+[!INCLUDE [create and manage scans](includes/view-and-manage-scans.md)]
+
+## Next steps
+
+Now that you have registered your source, follow the below guides to learn more about Purview and your data.
+
+- [Data insights in Azure Purview](concept-insights.md)
+- [Lineage in Azure Purview](catalog-lineage-user-guide.md)
+- [Search Data Catalog](how-to-search-catalog.md)