![]() Storage throttling occurs when the combined IOPS or throughput generated by applications, services, and serverless SQL pool workloads exceeds the limits of the storage account. Multiple applications and services might access your storage account. If they aren't in the same region, there will be increased latency for the data's network transfer between the remote region and the endpoint's region. Storage accounts and endpoints provisioned during workspace creation are located in the same region.įor optimal performance, if you access other storage accounts with serverless SQL pool, make sure they're in the same region. To minimize latency, colocate your Azure Storage account or Azure Cosmos DB analytic storage and your serverless SQL pool endpoint. Colocate your storage and serverless SQL pool ![]() Here are best practices for storage and content layout in serverless SQL pool. Use Azure Data Studio or SQL Server Management Studio to read a large amount of data. Azure Synapse Studio is a web tool that uses the HTTPS protocol to transfer data. Don't use Azure Synapse Studio to return a large amount of data.Make sure you don't have network bandwidth issues while reading a large amount of data. ![]() If you're reading data from your on-premises application, make sure the Azure Synapse workspace is in the region that's close to your location.Placing a client application and the Azure Synapse workspace in different regions could cause bigger latency and slower streaming of results. If needed, create the separate workspaces that are paired with your client applications. If you're using applications such as Power BI or Azure Analysis Service, make sure they're in the same region where you placed your Azure Synapse workspace. Colocate a client application with the Azure Synapse workspace.Make sure your client application is connected to the closest possible Azure Synapse workspace with the optimal connection. The numbers will drop if the queries are more complex or scan a larger amount of data, so in that case consider decreasing concurrency and execute queries over a longer period of time if possible.Ĭlient applications and network connections One serverless SQL pool can concurrently handle 1,000 active sessions that are executing lightweight queries. Maximum concurrency is not limited and depends on the query complexity and amount of data scanned.Serverless SQL pools can't provide an interactive experience in Power BI Direct Query mode if you're using complex queries or processing a large amount of data. Consider caching the results on the client side by using Power BI import mode or Azure Analysis Services, and periodically refresh them. ![]() For more information on changing collations, refer to Collation types supported for Synapse SQL.
0 Comments
Leave a Reply. |