Skip to content

Commit f6f03a3

Browse files
Added question about RCSI in dedicated SQL pools.
1 parent 727db0f commit f6f03a3

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/synapse-analytics/synapse-link/faq.yml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,4 +69,7 @@ sections:
6969
What type of encryption is applied to the landing zone?
7070
answer: |
7171
For Azure SQL Database, the landing zone is fully managed and is encrypted with the same key as the target Azure Synapse Analytics workspace - either platform-managed or customer-managed. For SQL Server 2022, the landing zone is customer-managed and can be encrypted with either a platform-managed key or a customer-managed key.
72-
72+
- question: |
73+
I updated all of the records in my source table. When I ran a query against the dedicated SQL pool I saw all of my data gone. I re-ran the query and all of the data was back - with the updates. Why does this happen?
74+
answer: |
75+
The ingestion service processes updates as a delete followed by an insert - all in the same transaction. By default, dedicated SQL pools run in READ UNCOMMITTED mode - which allows you to see the changes before the transaction has been committed. To ensure that you do not see these in-process changes, you can turn on READ COMMITTED SNAPSHOT ISOLATION.

0 commit comments

Comments
 (0)