Merge branch 'main' into jdaly-main-cors-msal

Author: JimDaly

.openpublishing.redirection.json

@@ -1,11 +1,16 @@
 {
   "redirections": [
-   {
+    {
       "source_path": "powerapps-docs/developer/data-platform/walkthrough-registering-configuring-simplespa-application-adal-js.md",
       "redirect_url": "quick-start-register-configure-simplespa-application-msal-js",
       "redirect_document_id": false
     }, 
-   {
+    {
+      "source_path": "powerapps-docs/maker/data-platform/azure-synapse-link-copy-sql.md",
+      "redirect_url": "azure-synapse-link-pipelines",
+      "redirect_document_id": false
+    },
+    {
       "source_path": "powerapps-docs/developer/data-platform/webapi/samples/cdswebapiservice.md",
       "redirect_url": "webapiservice",
       "redirect_document_id": false
@@ -7211,4 +7216,4 @@
       "redirect_document_id": "false"
     }
   ]
-}
+}

powerapps-docs/developer/data-platform/dataverse-sql-query.md

@@ -81,7 +81,7 @@ You can use the **Analyze in Power BI** option (**Data** > **Tables** > **Analyz
 
 Any operation that attempts to modify data (that is, INSERT, UPDATE) will not work with this read-only SQL data connection. For a detailed list of supported SQL operations on the Dataverse endpoint, see [How Dataverse SQL differs from Transact-SQL](how-dataverse-sql-differs-from-transact-sql.md).
 
-The following Dataverse datatypes are not supported with the SQL connection: `binary`, `image`, `sql_variant`, `varbinary`, `virtual`, `HierarchyId`, `managedproperty`, `file`, `xml`, `partylist`, `timestamp`, `choices`. In addition, tables types 'virtual' and 'audit' are not supported at this time. 
+The following Dataverse datatypes are not supported with the SQL connection: `binary`, `image`, `sql_variant`, `varbinary`, `virtual`, `HierarchyId`, `managedproperty`, `file`, `xml`, `partylist`, `timestamp`, `choices`. In addition, tables types 'virtual' and 'audit' are not supported at this time.
 
 > [!TIP]
 > `partylist` attributes can instead be queried by joining to the `activityparty` table as shown below.
@@ -181,8 +181,8 @@ This means the port has been blocked at the client.
 
 ### See also
 
+[Get started with virtual tables (entities)](./virtual-entities/get-started-ve.md)  
 [Use FetchXML to construct a query](dataverse-sql-query.md)  
 [Service Protection API Limits](api-limits.md)
 
-
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/how-dataverse-sql-differs-from-transact-sql.md

@@ -2,7 +2,7 @@
 title: "How Dataverse SQL Differs from Transact-SQL | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn what subset of the Transact-SQL language is supported by the Dataverse SQL endpoint." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 12/16/2020
+ms.date: 09/09/2022
 ms.reviewer: "pehecke"
 
 ms.topic: "article"
@@ -92,6 +92,7 @@ More information: [Transact-SQL statements](/sql/t-sql/statements/statements)
   - All WHERE conditions
   - All nested queries (SELECT, FROM, WHERE)
   - Union
+  - PIVOT and UNPIVOT
   - [GROUP BY](#select-group-by)/Having
 - General
   - IF THEN ELSE
@@ -106,7 +107,6 @@ More information: [Transact-SQL statements](/sql/t-sql/statements/statements)
 - DCL
 - Stored Procedure
 - DQL
-  - Pivot
   - DQL XML function
   - DQL JSON function
   - CUBE and ROLLUP

powerapps-docs/maker/TOC.yml

@@ -2548,7 +2548,7 @@
         href: ./data-platform/azure-synapse-link-create-view.md
       - name: Transform data with Apache Spark
         href: ./data-platform/azure-synapse-link-spark.md
-      - name: Run Azure Synapse pipelines
+      - name: Copy Dataverse into Azure SQL
         href: ./data-platform/azure-synapse-link-pipelines.md
       - name: Visualize data with Power BI
         href: ./data-platform/azure-synapse-link-powerbi.md
@@ -2562,8 +2562,6 @@
       items:
       - name: Ingest exported data with Azure Data Factory
         href: ./data-platform/export-to-data-lake-data-adf.md
-      - name: Copy data to Azure SQL with Azure Data Factory
-        href: ./data-platform/azure-synapse-link-copy-sql.md
       - name: Copy data from multiple data lakes to single data lake
         href: ./data-platform/azure-synapse-link-copy-mult-data-lakes.md
       - name: Transform data from CSV to Parquet

powerapps-docs/maker/data-platform/azure-synapse-link-copy-sql.md

@@ -41,31 +41,34 @@ This section describes the prerequisites necessary to create a view of your Data
 
 - **Synapse administrator.** You must be granted **Synapse Administrator** role access within Synapse studio.
 
-- **SQL Database.** This guide assumes you have created an additional SQL database (Serverless Pool or Dedicated Pool) in your Azure Synapse Analytics workspace to save the view.
 
 ## Create a view of your Dataverse data
 
 1. In Power Apps, select your Azure Synapse Link from the list, and then select **Go to Azure Synapse workspace**.
 
     ![Go to workspace.](media/go-to-workspace.png "Go to workspace")
 
-2. Expand **SQL database**, and select the **...** next to the database where you will store your view. Then select **New SQL script** > **New external table**.
+2. Create User-defined schema within Synapse SQL
 
-    ![New empty script.](media/new-empty-script.png "New empty script")
-
-3. Run a create view script by specifying a **view name**, the **column names**, **Dataverse database name**, and the exported **table name**.
+   ```sql
+   CREATE SCHEMA [SCHEMA NAME] 
+   GO
+   ```
+   
+3. Run a create view script by specifying a **view name**, the **column names**, **Dataverse database name** under the new **schema**, and then exported **table name**.
 
    ```sql
-   CREATE VIEW [VIEW NAME] 
+   CREATE OR ALTER VIEW [SCHEMA NAME].[VIEW NAME] 
    AS
    SELECT [COLUMN NAMES]
    FROM [DATAVERSE DATABASE NAME].[dbo].[TABLE NAME]
 
    ```
 
-4. Find the new view under the **Views** folder in the SQL database.
+## Use a view of your Dataverse data
 
-    ![Create view result.](media/create-view-result.png "Create view result")
+You can use views in your queries the same way you use views in SQL Server queries.
+The view will be created and accessible under views folder in **SQL Server Management Studio (SSMS)** or **Azure Data Studio**
 
 ### See also