You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/synapse-analytics/get-started.md
+25-29Lines changed: 25 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -403,7 +403,7 @@ ORDER BY
403
403
```
404
404
405
405
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;
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.
409
409
@@ -440,13 +440,13 @@ ORDER BY
440
440
441
441
```
442
442
After running this query, your output should look like this;
443
-

443
+

444
444
445
445
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.
446
446
## Create a virtual SQL database.
447
447
448
448
On the **Develop** hub click the **+** to add a new SQL **script**.
449
-

449
+

Ensure that when you run the query, that you are running it using the NYCTaxiVirtual database.
532
-

532
+

533
533
534
534
### Visualize with Power BI
535
535
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.
536
536
On the **Develop** hub, expand your linked workspace under **Power BI** and click on **Power BI Datasets**.
537
537
538
-

538
+

539
539
540
540
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**.
541
541
542
-

542
+

543
543
544
544
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.
545
545
546
-

546
+

547
547
548
548
Select **NYCTaxiVirtual** and click continue.
549
549
550
-

550
+

551
551
552
552
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**.
553
553
554
-

554
+

555
555
556
556
Select all the views to include in your Power BI dataset and click **Load**.
557
557
558
-

558
+

Click on the **Model** view and create relationships between the three tables by dragging **DateID** from **Trips** and dropping it on **DateID** in **dimDate**.
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.
Change the **Authentication method** to **OAuth2** and click **Sign in**. Sign in with your Azure Active Directory Account.
603
603
604
-

604
+

605
605
606
606
After publishing, switch back to Synapse Studio and click **Close and refresh**.
607
607
608
-

608
+

609
609
610
610
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.
Copy file name to clipboardExpand all lines: articles/synapse-analytics/overview-faq.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,8 +30,7 @@ A: Azure Synapse is an integrated data platform for BI, AI, and continuous intel
30
30
31
31
### Q: How do I get started with Azure Synapse Analytics
32
32
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.
35
34
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:
Copy file name to clipboardExpand all lines: articles/synapse-analytics/quickstart-create-workspace.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,9 @@ If you don't have an Azure subscription, [create a free account before you begin
21
21
22
22
-[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)
23
23
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
+
24
27
## Sign in to the Azure portal
25
28
26
29
Sign in to the [Azure portal](https://portal.azure.com/)
Copy file name to clipboardExpand all lines: articles/synapse-analytics/security/how-to-connect-to-workspace-with-private-links.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,19 +13,24 @@ ms.reviewer: jrasnick
13
13
14
14
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.
15
15
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
17
22
18
23
Select **Private endpoint connection** under **Security** and then select **+ Private endpoint**.
19
24

20
25
21
-
## Step 2: Select your subscription and region details
26
+
## Step 3: Select your subscription and region details
22
27
23
28
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.
24
29
25
30
Private endpoints are created in a subnet. The subscription, resource group, and region selected filter the private endpoint subnets. Select **Next: Resource >** when done.
26
31

27
32
28
-
## Step 3: Select your Azure Synapse workspace details
33
+
## Step 4: Select your Azure Synapse workspace details
29
34
30
35
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*.
Copy file name to clipboardExpand all lines: articles/synapse-analytics/security/synapse-workspace-managed-private-endpoints.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,8 +27,9 @@ Private endpoint uses a private IP address from your VNet to effectively bring t
27
27
28
28
>[!IMPORTANT]
29
29
>Managed private endpoints are only supported in Azure Synapse workspaces with a Managed workspace VNet.
30
+
30
31
>[!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.
32
33
33
34
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.
Copy file name to clipboardExpand all lines: articles/synapse-analytics/security/synapse-workspace-managed-vnet.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,6 +37,8 @@ SQL pool and SQL on-demand are multi-tenant capabilities and therefore reside ou
37
37
38
38
## Create an Azure Synapse workspace with a Managed workspace VNet
39
39
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
+
40
42
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.
41
43
42
44
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
>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.
51
53
52
54
You can check whether your Azure Synapse workspace is associated to a Managed workspace VNet by selecting **Overview** from Azure portal.
0 commit comments