Skip to content

Commit 08b21ec

Browse files
authored
Merge pull request #281936 from MicrosoftDocs/main
Publish to live, Friday 4 AM PST, 7/26
2 parents fa5291a + 06271bc commit 08b21ec

File tree

9 files changed

+16
-11
lines changed

9 files changed

+16
-11
lines changed

articles/data-factory/connector-snowflake.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: data-factory
88
ms.subservice: data-movement
99
ms.topic: conceptual
1010
ms.custom: synapse
11-
ms.date: 06/24/2024
11+
ms.date: 07/25/2024
1212
---
1313

1414
# Copy and transform data in Snowflake using Azure Data Factory or Azure Synapse Analytics
@@ -679,8 +679,10 @@ To determine the version of the Snowflake connector used in your existing Snowfl
679679

680680
The V2 version offers several enhancements over the legacy version, including:
681681

682-
Autoscaling: Automatically adjusts resources based on traffic load.
683-
Multi-Availability Zone Operation: Provides resilience by operating across multiple availability zones.
682+
Autoscaling: Automatically adjusts resources based on traffic load.<br/>
683+
684+
Multi-Availability Zone Operation: Provides resilience by operating across multiple availability zones.<br/>
685+
684686
Static IP Support: Enhances security by allowing the use of static IP addresses.
685687

686688
## Related content

articles/data-factory/connector-troubleshoot-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -250,9 +250,9 @@ The errors below are general to the copy activity and could occur with any conne
250250

251251
#### Error code: 11775
252252

253-
- **Message**: `Failed to connect to your instance of Azure Database for PostgreSQL flexible server.`
253+
- **Message**: `Failed to connect to your instance of Azure Database for PostgreSQL flexible server. '%'`
254254

255-
- **Cause**: User or password provided are incorrect. The encryption method selected is not compatible with the configuration of the server. The network connectivity method configured for your instance doesn't allow connections from the Integration Runtime selected.
255+
- **Cause**: Exact cause depends on the text returned in `'%'`. If it is **The operation has timed out**, it can be because the instance of PostgreSQL is stopped or because the network connectivity method configured for your instance doesn't allow connections from the Integration Runtime selected. User or password provided are incorrect. If it is **28P01: password authentication failed for user "*youruser*"**, it means that the user provided doesn't exist in the instance or that the password is incorrect. If it is **28000: no pg_hba.conf entry for host "*###.###.###.###*", user "*youruser*", database "*yourdatabase*", no encryption**, it means that the encryption method selected is not compatible with the configuration of the server.
256256

257257
- **Recommendation**: Confirm that the user provided exists in your instance of PostgreSQL and that the password corresponds to the one currently assigned to that user. Make sure that the encryption method selected is accepted by your instance of PostgreSQL, based on its current configuration. If the network connectivity method of your instance is configured for Private access (VNet integration), use a Self-Hosted Integration Runtime (IR) to connect to it. If it is configured for Public access (allowed IP addresses), it is recommended to use an Azure IR with managed virtual network and deploy a managed private endpoint to connect to your instance. When it is configured for Public access (allowed IP addresses) a less recommended alternative consists in creating firewall rules in your instance to allow traffic originating on the IP addresses used by the Azure IR you're using.
258258

articles/postgresql/flexible-server/how-to-restore-server-portal.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article describes how to perform restore operations in Azure D
44
author: AwdotiaRomanowna
55
ms.author: alkuchar
66
ms.reviewer: maghan
7-
ms.date: 04/27/2024
7+
ms.date: 07/26/2024
88
ms.service: postgresql
99
ms.subservice: flexible-server
1010
ms.topic: how-to
@@ -52,7 +52,7 @@ Follow these steps to restore your Azure Database for PostgreSQL flexible server
5252

5353
5. Under **Server details**, for **Name**, provide a server name. For **Availability zone**, you can optionally choose an availability zone to restore to.
5454

55-
:::image type="content" source="./media/how-to-restore-server-portal/restore-custom-2.png" alt-text="Screenshot that shows selections for restoring to a custom restore point.":::
55+
:::image type="content" source="./media/how-to-restore-server-portal/restore-custom.png" alt-text="Screenshot that shows selections for restoring to a custom restore point.":::
5656

5757
6. Select **OK**. A notification shows that the restore operation has started.
5858

@@ -85,9 +85,9 @@ If your source server is configured with geo-redundant backup, you can restore t
8585

8686
2. Select **Overview** from the left pane, and then select **Restore**.
8787

88-
:::image type="content" source="./media/how-to-restore-server-portal/geo-restore-click.png" alt-text="Screenshot that shows the Restore button.":::
88+
:::image type="content" source="./media/how-to-restore-server-portal/restore-overview.png" alt-text="Screenshot that shows the Restore button.":::
8989

90-
3. Under **Source details**, for **Geo-redundant restore**, select the **Restore to paired region** checkbox.
90+
3. Under **Source details**, for **Geo-redundant restore (preview)**, select the **Restore to paired region** checkbox.
9191

9292
:::image type="content" source="./media/how-to-restore-server-portal/geo-restore-choose-checkbox.png" alt-text="Screenshot that shows the option for restoring to a paired region for geo-redundant restore.":::
9393

116 KB
Loading
48.4 KB
Loading
153 KB
Loading
111 KB
Loading
35.7 KB
Loading

articles/synapse-analytics/spark/apache-spark-development-using-notebooks.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ The IntelliSense features are at different levels of maturity for different lang
143143
144144
<h3 id="code-snippets">Code Snippets</h3>
145145

146-
Synapse notebooks provide code snippets that make it easier to enter common used code patterns, such as configuring your Spark session, reading data as a Spark DataFrame, or drawing charts with matplotlib etc.
146+
Synapse notebooks provide code snippets that make it easier to enter commonly used code patterns, such as configuring your Spark session, reading data as a Spark DataFrame, or drawing charts with matplotlib etc.
147147

148148
Snippets appear in [Shortcut keys of IDE style IntelliSense](#ide-style-intellisense) mixed with other suggestions. The code snippets contents align with the code cell language. You can see available snippets by typing **Snippet** or any keywords appear in the snippet title in the code cell editor. For example, by typing **read** you can see the list of snippets to read data from various data sources.
149149

@@ -240,6 +240,9 @@ The Outlines (Table of Contents) presents the first markdown header of any markd
240240

241241
You can run the code cells in your notebook individually or all at once. The status and progress of each cell is represented in the notebook.
242242

243+
> [!NOTE]
244+
> Deleting a notebook will not automatically cancel any jobs that are currently running. If you need to cancel a job, you should visit the Monitoring Hub and cancel it manually.
245+
243246
### Run a cell
244247

245248
There are several ways to run the code in a cell.
@@ -306,7 +309,7 @@ You can select the **Variables** button on the notebook command bar to open or h
306309

307310
### Cell status indicator
308311

309-
A step-by-step cell execution status is displayed beneath the cell to help you see its current progress. Once the cell run is complete, an execution summary with the total duration and end time are shown and kept there for future reference.
312+
A step-by-step cell execution status is displayed beneath the cell to help you see its current progress. Once the cell run is complete, an execution summary with the total duration and end time is shown and kept there for future reference.
310313

311314
![Screenshot of cell-status](./media/apache-spark-development-using-notebooks/synapse-cell-status.png)
312315

0 commit comments

Comments
 (0)