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/data-share/how-to-share-from-sql.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -358,12 +358,16 @@ For source SQL tables with dynamic data masking, data will appear masked on the
358
358
## SQL snapshot performance
359
359
SQL snapshot performance is impacted by a number of factors. It is always recommended to conduct your own performance testing. Below are some example factors impacting performance.
360
360
361
+
* Source or destination data store input/output operations per second (IOPS) and bandwidth.
361
362
* Hardware configuration (e.g. vCores, memory, DWU) of the source and target SQL data store.
362
-
* Concurrent access to the source and target data stores. If you are sharing multiple tables and views from the same SQL data store, or receive multiple tables and views into the same SQL data store, performance will be impacted.
363
-
* Location of source and target data stores.
363
+
* Concurrent access to the source and target data stores. If you are sharing multiple tables and views from the same SQL data store, or receive multiple tables and views into the same SQL data store, performance will be impacted.
364
+
* Network bandwidth between the source and destination data stores, and location of source and target data stores.
365
+
* Size of the tables and views being shared. SQL snapshot sharing does a full copy of the entire table. If the size of the table grows over time, snapshot will take longer.
366
+
367
+
For large tables where incremental updates are desired, you can export updates to storage account and leverage storage account’s incremental sharing capability for faster performance.
364
368
365
369
## Troubleshoot SQL snapshot failure
366
370
The most common cause of snapshot failure is that Data Share does not have permission to the source or target data store. In order to grant Data Share permission to the source or target Azure SQL Database or Azure Synapse Analytics (formerly Azure SQL DW), you must run the provided SQL script when connecting to the SQL database using Azure Active Directory authentication. To troubleshoot additional SQL snapshot failure, refer to [Troubleshoot snapshot failure](data-share-troubleshoot.md#snapshots).
367
371
368
372
## Next steps
369
-
You have learned how to share and receive data from SQL sources using Azure Data Share service. To learn more about sharing from other data sources, continue to [supported data stores](supported-data-stores.md).
373
+
You have learned how to share and receive data from SQL sources using Azure Data Share service. To learn more about sharing from other data sources, continue to [supported data stores](supported-data-stores.md).
0 commit comments