Skip to content

Commit b2b0ea1

Browse files
committed
Merge branch 'release-synapse-current' of https://github.com/MicrosoftDocs/azure-docs-pr into 20200513_fixtypos
2 parents e509b95 + a3dec93 commit b2b0ea1

12 files changed

+81
-64
lines changed

articles/synapse-analytics/get-started.md

Lines changed: 25 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -403,7 +403,7 @@ ORDER BY
403403
```
404404

405405
If you are a user of T-SQL, this syntax will be identical to what you are used to using. This query selects three aggregations from the **Trip** Parquet file and groups them by DateId and PickupGeographyId. After running the query, you should see and output like this;
406-
![Simple aggregation query](./media/get-started-synapse-analytics/sql-simple-agg-output.PNG)
406+
![Simple aggregation query](./media/get-started-synapse-analytics/sql-simple-agg-output.png)
407407

408408
You can make the results easier to read, by replacing DateId and PickupGeographyId with the actual date and pickup city. This values can be obtained by joining to the **Date** and **Geography** files.
409409

@@ -440,13 +440,13 @@ ORDER BY
440440

441441
```
442442
After running this query, your output should look like this;
443-
![Aggregation query with joins](./media/get-started-synapse-analytics/sql-joins-agg-output.PNG)
443+
![Aggregation query with joins](./media/get-started-synapse-analytics/sql-joins-agg-output.png)
444444

445445
As you can see, multiple Parquet files can be joined almost as if they were actual SQL views. If you find the **OPENROWSET** syntax a little harder to user to use than regular SQL views, you can solve this by creating a virtual SQL database with SQL views.
446446
## Create a virtual SQL database.
447447

448448
On the **Develop** hub click the **+** to add a new SQL **script**.
449-
![Create new SQL script](./media/get-started-synapse-analytics/sql-new-script.PNG)
449+
![Create new SQL script](./media/get-started-synapse-analytics/sql-new-script.png)
450450

451451
To create the database run the following script;
452452

@@ -455,13 +455,13 @@ CREATE DATABASE NYCTaxiVirtual;
455455
```
456456

457457
Now, if you flip to the data hub, you will see the newly created database.
458-
![See created database](./media/get-started-synapse-analytics/sql-data-see-db.PNG)
458+
![See created database](./media/get-started-synapse-analytics/sql-data-see-db.png)
459459

460460
## Create SQL views
461461

462462
Create a new SQL script which uses the NYCTaxiVirtual database by right clicking on the database name and selecting **New SQL script**.
463463

464-
![Create new SQL script from database](./media/get-started-synapse-analytics/sql-new-script-from-db.PNG)
464+
![Create new SQL script from database](./media/get-started-synapse-analytics/sql-new-script-from-db.png)
465465

466466
Run SQL statements like the following for each view that you wish to create.
467467

@@ -499,7 +499,7 @@ FROM
499499
```
500500

501501
After the views are created, you can expand the NYCTaxiVirtual database in the data hub to see the views and their schema.
502-
![View database schema](./media/get-started-synapse-analytics/sql-expand-db.PNG)
502+
![View database schema](./media/get-started-synapse-analytics/sql-expand-db.png)
503503

504504
## Query the SQL views
505505

@@ -529,53 +529,53 @@ ORDER BY
529529
```
530530

531531
Ensure that when you run the query, that you are running it using the NYCTaxiVirtual database.
532-
![Run updated query in correct database](./media/get-started-synapse-analytics/sql-run-query-in-db.PNG)
532+
![Run updated query in correct database](./media/get-started-synapse-analytics/sql-run-query-in-db.png)
533533

534534
### Visualize with Power BI
535535
Your data can now be easily analyzed and visualized in Power BI. Synapse offers a unique integration which allows you to link a Power BI workspace to you Synapse workspace. Before going forward, follow the steps in this [quickstart](quickstart-power-bi.md) to link your Power BI workspace.
536536
On the **Develop** hub, expand your linked workspace under **Power BI** and click on **Power BI Datasets**.
537537

538-
![View Power BI datasets](./media/get-started-synapse-analytics/pbi-view-datasets.PNG)
538+
![View Power BI datasets](./media/get-started-synapse-analytics/pbi-view-datasets.png)
539539

540540
Any existing datasets from you linked Power BI workspace will be displayed here. You can create new reports in Synapse Studio using these Power BI datasets. Let’s create a new Power BI dataset for the virtual database which we created in the last section. Click **+ New Power BI dataset**.
541541

542-
![New Power BI datasets](./media/get-started-synapse-analytics/pbi-new-dataset.PNG)
542+
![New Power BI datasets](./media/get-started-synapse-analytics/pbi-new-dataset.png)
543543

544544
While Power BI reports can be created in Synapse Studio, Power BI datasets must be created in the Power BI Desktop. Install the Power BI Desktop if you have not already and then click **Start** once the installation is complete.
545545

546-
![Download Power BI Desktop](./media/get-started-synapse-analytics/pbi-download-desktop.PNG)
546+
![Download Power BI Desktop](./media/get-started-synapse-analytics/pbi-download-desktop.png)
547547

548548
Select **NYCTaxiVirtual** and click continue.
549549

550-
![Select database to use](./media/get-started-synapse-analytics/pbi-select-database.PNG)
550+
![Select database to use](./media/get-started-synapse-analytics/pbi-select-database.png)
551551

552552
Click **Download** to download the Power BI dataset file (pbids). Open the file when the download is complete to launch the Power BI Desktop. Once the Power BI Desktop has been launched, sign into Synapse by using your Azure Active Directory user account. Then click **Connect**.
553553

554-
![Sign into Synapse](./media/get-started-synapse-analytics/pbi-sign-in.PNG)
554+
![Sign into Synapse](./media/get-started-synapse-analytics/pbi-sign-in.png)
555555

556556
Select all the views to include in your Power BI dataset and click **Load**.
557557

558-
![Select all views in the navigator](./media/get-started-synapse-analytics/pbi-navigator.PNG)
558+
![Select all views in the navigator](./media/get-started-synapse-analytics/pbi-navigator.png)
559559

560560
Select **DirectQuery** and click **OK**.
561561

562-
![Select DirectQuery](./media/get-started-synapse-analytics/pbi-directquery.PNG)
562+
![Select DirectQuery](./media/get-started-synapse-analytics/pbi-directquery.png)
563563

564564
Click on the **Model** view and create relationships between the three tables by dragging **DateID** from **Trips** and dropping it on **DateID** in **dimDate**.
565565

566-
![Create relationships](./media/get-started-synapse-analytics/pbi-create-relationship.PNG)
566+
![Create relationships](./media/get-started-synapse-analytics/pbi-create-relationship.png)
567567

568568
Click **Assume referential integrity** and click **OK**.
569569

570-
![Setup relationship](./media/get-started-synapse-analytics/pbi-ref-integrity.PNG)
570+
![Setup relationship](./media/get-started-synapse-analytics/pbi-ref-integrity.png)
571571

572572
Create another relationship by dragging **PickupGepgraphyID** from **Trips** and dropping it on **GeographyID** on **dimGeography**. Select **Assume referential integrity** like in the last step. Your model diagram should now look something like below.
573573

574-
![Relationship diagram](./media/get-started-synapse-analytics/pbi-diagram.PNG)
574+
![Relationship diagram](./media/get-started-synapse-analytics/pbi-diagram.png)
575575

576576
Go back to the **Report** view and right-click on the **Trips** table and click on **New Measure**.
577577

578-
![New measure](./media/get-started-synapse-analytics/pbi-new-measure.PNG)
578+
![New measure](./media/get-started-synapse-analytics/pbi-new-measure.png)
579579

580580
Enter the following DAX formula into the formula bar and press enter.
581581
```dax
@@ -585,35 +585,31 @@ Average fair per trip = DIVIDE(
585585
)
586586
```
587587

588-
![Formula bar](./media/get-started-synapse-analytics/pbi-formula.PNG)
588+
![Formula bar](./media/get-started-synapse-analytics/pbi-formula.png)
589589

590590
Save the Power BI File and publish it to the Power BI workspace that you linked to Synapse.
591591

592-
![Publish to workspace](./media/get-started-synapse-analytics/pbi-publish.PNG)
592+
![Publish to workspace](./media/get-started-synapse-analytics/pbi-publish.png)
593593

594594
After publishing, go to the **Settings** page for your Power BI dataset inside of your Power BI workspace.
595595

596-
![Dataset settings](./media/get-started-synapse-analytics/pbi-find-dataset-settings.PNG)
596+
![Dataset settings](./media/get-started-synapse-analytics/pbi-find-dataset-settings.png)
597597

598598
Under **Data source credentials** hit **Edit credentials**.
599599

600-
![Edit credentials](./media/get-started-synapse-analytics/pbi-edit-credentials.PNG)
600+
![Edit credentials](./media/get-started-synapse-analytics/pbi-edit-credentials.png)
601601

602602
Change the **Authentication method** to **OAuth2** and click **Sign in**. Sign in with your Azure Active Directory Account.
603603

604-
![Sign into Synapse](./media/get-started-synapse-analytics/pbi-web-sign-in.PNG)
604+
![Sign into Synapse](./media/get-started-synapse-analytics/pbi-web-sign-in.png)
605605

606606
After publishing, switch back to Synapse Studio and click **Close and refresh**.
607607

608-
![Close and refresh](./media/get-started-synapse-analytics/pbi-close-refresh.PNG)
608+
![Close and refresh](./media/get-started-synapse-analytics/pbi-close-refresh.png)
609609

610610
Click **New Power BI report** next to the name of the Power BI dataset that you just published. Now you can build out your Power BI report direction in Synapse Studio. Don’t forget to save the report when you are finished creating it.
611611

612-
![Save report](./media/get-started-synapse-analytics/pbi-save-report.PNG)
613-
614-
<!--## Serve via SQL pool--->
615-
<!--- Matthew
616-
--->
612+
![Save report](./media/get-started-synapse-analytics/pbi-save-report.png)
617613

618614

619615
## Orchestrate using a pipeline

articles/synapse-analytics/overview-faq.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,7 @@ A: Azure Synapse is an integrated data platform for BI, AI, and continuous intel
3030

3131
### Q: How do I get started with Azure Synapse Analytics
3232

33-
A: To start using Azure Synapse Analytics, create a [Synapse workspace](https://portal.azure.com) (it's free!) and create the resources that you want under that workspace. You can follow one of our quickstart tutorials, such as [Create a Synapse SQL pool](quickstart-create-sql-pool-portal.md) or [Create a workspace](quickstart-create-workspace.md), that will walk you through simple use case.
34-
33+
A: To start using Azure Synapse Analytics, [register Azure Synapse resource provider](https://docs.microsoft.com/azure/azure-resource-manager/management/resource-providers-and-types) by selecting *Microsoft.Synapse* from the list of resource providers. Then create a [Synapse workspace](https://portal.azure.com) (it's free!) and create the resources that you want under that workspace. You can follow one of our quickstart tutorials, such as [Create a Synapse SQL pool](quickstart-create-sql-pool.md) or [Create a workspace](quickstart-create-workspace.md), that will walk you through simple use case.
3534
You can also find sample notebooks and SQL scripts in our [repository](https://github.com/Azure/azure-synapse-analytics/tree/master/samples). If you need to connect to a public dataset, create a new linked service with the following attributes:
3635

3736
- azure_storage_account_name = "azureopendatastorage"

articles/synapse-analytics/quickstart-create-workspace.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,9 @@ If you don't have an Azure subscription, [create a free account before you begin
2121

2222
- [Azure Data Lake Storage Gen2 storage account](../storage/common/storage-account-create.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json)
2323

24+
## Register Azure Synapse resource provider
25+
If you have not already done so, register Azure Synapse resource provider. Registering a resource provider configures your subscription to work with the resource provider. For registering Azure Synapse resource provider, see [Azure resource providers and types](https://docs.microsoft.com/azure/azure-resource-manager/management/resource-providers-and-types). Choose *Microsoft.Synapse* from the list of resource providers when you register.
26+
2427
## Sign in to the Azure portal
2528

2629
Sign in to the [Azure portal](https://portal.azure.com/)

articles/synapse-analytics/security/how-to-connect-to-workspace-with-private-links.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,19 +13,24 @@ ms.reviewer: jrasnick
1313

1414
This article will teach you how to create private endpoint to your Azure Synapse workspace. See [private links and private endpoints](https://docs.microsoft.com/azure/private-link/) to learn more.
1515

16-
## Step 1: Open your Azure Synapse workspace in Azure portal
16+
## Step 1: Register Network resource provider
17+
18+
If you have not already done so, register the Network resource provider. Registering a resource provider configures your subscription to work with the resource provider. Choose *Microsoft.Network* from the list of resource providers when you [register](https://docs.microsoft.com/azure/azure-resource-manager/management/resource-providers-and-types). If the Network resource provider is already registered, then proceed to Step 2.
19+
20+
21+
## Step 2: Open your Azure Synapse workspace in Azure portal
1722

1823
Select **Private endpoint connection** under **Security** and then select **+ Private endpoint**.
1924
![Open Azure Synapse workspace in Azure portal](./media/how-to-connect-to-workspace-with-private-links/private-endpoint-1.png)
2025

21-
## Step 2: Select your subscription and region details
26+
## Step 3: Select your subscription and region details
2227

2328
Under the **Basics** tab in the **Create a private endpoint** window, choose your **Subscription** and **Resource Group**. Give a **Name** to the private endpoint that you want to create. Select the **Region** where you want the private endpoint created.
2429

2530
Private endpoints are created in a subnet. The subscription, resource group, and region selected filter the private endpoint subnets. Select **Next: Resource >** when done.
2631
![Select subscription and region details](./media/how-to-connect-to-workspace-with-private-links/private-endpoint-2.png)
2732

28-
## Step 3: Select your Azure Synapse workspace details
33+
## Step 4: Select your Azure Synapse workspace details
2934

3035
Select **Connect to an Azure resource in my directory** in the **Resource** tab. Select the **Subscription** that contains your Azure Synapse workspace. The **Resource type** for creating private endpoints to an Azure Synapse workspace is *Microsoft.Synapse/workspaces*.
3136

articles/synapse-analytics/security/synapse-workspace-managed-private-endpoints.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,9 @@ Private endpoint uses a private IP address from your VNet to effectively bring t
2727

2828
>[!IMPORTANT]
2929
>Managed private endpoints are only supported in Azure Synapse workspaces with a Managed workspace VNet.
30+
3031
>[!NOTE]
31-
>It's recommended that you create Managed private endpoints to connect to all your Azure data sources. All outbound traffic from the >Managed workspace VNet will be blocked in the future.
32+
>All outbound traffic from the Managed workspace VNet except through Managed private endpoints will be blocked in the future. It's recommended that you create Managed private endpoints to connect to all your Azure data sources external to the workspace.
3233
3334
A private endpoint connection is created in a "Pending" state when you create a Managed private endpoint in Azure Synapse. An approval workflow is initiated. The private link resource owner is responsible to approve or reject the connection.
3435

articles/synapse-analytics/security/synapse-workspace-managed-vnet.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,8 @@ SQL pool and SQL on-demand are multi-tenant capabilities and therefore reside ou
3737
3838
## Create an Azure Synapse workspace with a Managed workspace VNet
3939

40+
If you have not already done so, register the Network resource provider. Registering a resource provider configures your subscription to work with the resource provider. Choose *Microsoft.Network* from the list of resource providers when you [register](https://docs.microsoft.com/azure/azure-resource-manager/management/resource-providers-and-types).
41+
4042
To create an Azure Synapse workspace that has a Managed workspace VNet associated with it, select the **Security + networking** tab in Azure portal and check the **Enable managed virtual network** checkbox.
4143

4244
If you leave the checkbox unchecked, then your workspace won't have a VNet associated with it.
@@ -47,7 +49,7 @@ If you leave the checkbox unchecked, then your workspace won't have a VNet assoc
4749
![Enable Managed workspace VNet](./media/synapse-workspace-managed-vnet/enable-managed-vnet-1.png)
4850

4951
>[!NOTE]
50-
>All outbound traffic from the Managed workspace VNet will be blocked in the future. It's recommended that you connect to all your data sources using Managed private endpoints.
52+
>All outbound traffic from the Managed workspace VNet except through Managed private endpoints will be blocked in the future. It's recommended that you create Managed private endpoints to connect to all your Azure data sources external to the workspace.
5153
5254
You can check whether your Azure Synapse workspace is associated to a Managed workspace VNet by selecting **Overview** from Azure portal.
5355

0 commit comments

Comments
 (0)