Skip to content

Commit 1ea0228

Browse files
authored
Merge pull request #185927 from MicrosoftDocs/master
Merge master to live, 4 AM
2 parents 2a39d46 + e24af21 commit 1ea0228

File tree

5 files changed

+34
-9
lines changed

5 files changed

+34
-9
lines changed

articles/azure-sql/managed-instance/long-term-backup-retention-configure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.date: 09/12/2021
1515
# Manage Azure SQL Managed Instance long-term backup retention
1616
[!INCLUDE[appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
1717

18-
In Azure SQL Managed Instance, you can configure a [long-term backup retention](../database/long-term-retention-overview.md) policy (LTR) as a public preview feature. This allows you to automatically retain database backups in separate Azure Blob storage containers for up to 10 years. You can then recover a database using these backups with the Azure portal and PowerShell.
18+
In Azure SQL Managed Instance, you can configure a [long-term backup retention](../database/long-term-retention-overview.md) policy (LTR). This allows you to automatically retain database backups in separate Azure Blob storage containers for up to 10 years. You can then recover a database using these backups with the Azure portal and PowerShell.
1919

2020
The following sections show you how to use the Azure portal, PowerShell, and Azure CLI to configure the long-term backup retention, view backups in Azure SQL storage, and restore from a backup in Azure SQL storage.
2121

articles/data-factory/concepts-data-flow-performance-sinks.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,9 @@ With Azure SQL Database, the default partitioning should work in most cases. The
2121

2222
### Best practice for deleting rows in sink based on missing rows in source
2323

24-
Here is a video walk through of how to use data flows with exits, alter row, and sink transformations to achieve this common pattern: > [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RWMLr5]
24+
Here is a video walk through of how to use data flows with exits, alter row, and sink transformations to achieve this common pattern:
25+
26+
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RWMLr5]
2527
2628
### Impact of error row handling to performance
2729

articles/data-factory/data-flow-troubleshoot-connector-format.md

Lines changed: 24 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
title: Troubleshoot connector and format issues in mapping data flows
33
description: Learn how to troubleshoot data flow problems related to connector and format in Azure Data Factory.
4-
author: linda33wj
5-
ms.author: jingwang
4+
author: jianleishen
5+
ms.author: jianleishen
66
ms.reviewer: wiassaf
77
ms.service: data-factory
88
ms.subservice: data-flows
99
ms.topic: troubleshooting
10-
ms.date: 12/06/2021
10+
ms.date: 01/21/2022
1111
---
1212

1313

@@ -457,6 +457,27 @@ You use the Azure Blob Storage as the staging linked service to link to a storag
457457
#### Recommendation
458458
Create an Azure Data Lake Gen2 linked service for the storage, and select the Gen2 storage as the staging linked service in data flow activities.
459459

460+
### Failed with an error: "shaded.msdataflow.com.microsoft.sqlserver.jdbc.SQLServerException: User does not have permission to perform this action."
461+
462+
#### Symptoms
463+
464+
When you use Azure Synapse Analytics as a source/sink and use PolyBase staging in data flows, you meet the following error: <br/>
465+
466+
`shaded.msdataflow.com.microsoft.sqlserver.jdbc.SQLServerException: User does not have permission to perform this action.`
467+
468+
#### Cause
469+
470+
PolyBase requires certain permissions in your Synapse SQL server to work.
471+
472+
#### Recommendation
473+
474+
Grant the permissions below in your Synapse SQL server when you use PolyBase:
475+
476+
**ALTER ANY SCHEMA**<br/>
477+
**ALTER ANY EXTERNAL DATA SOURCE**<br/>
478+
**ALTER ANY EXTERNAL FILE FORMAT**<br/>
479+
**CONTROL DATABASE**<br/>
480+
460481
## Common Data Model format
461482

462483
### Model.json files with special characters

articles/databox-online/azure-stack-edge-gpu-data-residency.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The single region data residency option is available only for Southeast Asia (Si
3030
The data residency posture of the Azure Stack Edge services can be summarized for the following aspects of the service:
3131

3232
- Existing Azure Stack Edge ordering and management service.
33-
- New Azure Edge Hardware Center (Preview) that will be used for new orders going forward.
33+
- New Azure Edge Hardware Center that will be used for new orders going forward.
3434
<!--- Telemetry for the device and the service.
3535
- Proactive Support log collection where any logs that the service generates are stored in a single region and are not replicated to the paired region.-->
3636

@@ -40,6 +40,8 @@ Azure Stack Edge service also integrates with the following dependent services a
4040
- Azure IoT Hub and Azure IoT Edge
4141
<!--- Azure Key Vault -->
4242

43+
> [!NOTE]
44+
> - If you provide a support package with a crash dump for the Azure Stack Edge device, it can contain End User Identifiable Information (EUII) or End User Pseudonymous Information (EUPI) which will be processed and stored outside South East Asia.
4345
4446
## Azure Stack Edge classic ordering and management resource
4547

@@ -53,7 +55,7 @@ If you are creating a new Azure Stack Edge resource, you have the option to enab
5355

5456
## Azure Edge Hardware Center ordering and management resource
5557

56-
The new Azure Edge Hardware Center service (Preview) is now available and allows you to create and manage Azure Stack Edge resources. When placing an order in Southeast Asia region, you can select the option to have your data resides only within Singapore and not be replicated.
58+
The new Azure Edge Hardware Center service is now available and allows you to create and manage Azure Stack Edge resources. When placing an order in Southeast Asia region, you can select the option to have your data resides only within Singapore and not be replicated.
5759

5860
In the event of region-wide outages, you won’t be able to access the order resources. You will not be able to return, cancel, or delete the resources. If you request for updates on your order status or need to initiate a device return urgently during the service outage, Microsoft Support will handle those requests.
5961

@@ -99,4 +101,4 @@ If you choose to store and process the data only in Singapore region, then the s
99101

100102
## Next steps
101103

102-
- Learn more about [Azure data residency requirements](https://azure.microsoft.com/global-infrastructure/data-residency/).
104+
- Learn more about [Azure data residency requirements](https://azure.microsoft.com/global-infrastructure/data-residency/).

articles/sentinel/whats-new.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ If you're looking for items older than six months, you'll find them in the [Arch
2727
>
2828
> You can also contribute! Join us in the [Microsoft Sentinel Threat Hunters GitHub community](https://github.com/Azure/Azure-Sentinel/wiki).
2929
30-
## January 2021
30+
## January 2022
3131

3232
- [SentinelHealth data table (Public preview)](#sentinelhealth-data-table-public-preview)
3333
- [More workspaces supported for Multiple Workspace View](#more-workspaces-supported-for-multiple-workspace-view)

0 commit comments

Comments
 (0)