一个Azure SQL数据库与多个 [英] One Azure SQL Database vs multiple
问题描述
我们的传统本地SQL Server目前正在使用具有大量跨数据库查询的多数据库架构。
迁移到Azure SQL数据库会出现跨数据库查询的问题。 有一个Azure SQL数据库弹性查询，但我想知道与内部SQL Server相比的性能，其中所有跨数据库查询在同一物理SQL Server和实例上命中数据库
。 例如，Azure SQL数据库弹性查询是否与从性能角度使用链接服务器相当？
因此，对于Azure SQL数据库，使用Azure SQL的多数据库体系结构是否正常？数据库弹性查询，或者，我们应该坚持使用单个Azure SQL数据库并使用模式在单个Azure SQL数据库中细分？ 假设
最大数据库大小不是我们将遇到的。
谢谢
你好，b
如果弹性查询被参数化，那么他们将参数化操作推送到远程数据库，避免检索
大行集，并将显示良好的性能。每当弹性查询需要传输大行集时，您会看到性能不佳。
您可以考虑的一件事是将所有数据库统一为一个（如您所述）并为每个数据库创建单独的架构。这样，您将避免在数据库之间传输大型行集的性能影响。
希望这会有所帮助。
问候，
Alberto Morillo
SQLCoffee.com
Hi,
Our legacy on-prem SQL Server is currently using a multiple database architecture with a lot of cross database queries.
Moving to Azure SQL Database presents a problem for cross database queries. There is Azure SQL Database elastic query, but I am wondering about the performance of that compared to an on-prem SQL Server where all cross database queries hit databases on the same physical SQL Server and instance. For example, is Azure SQL Database elastic query comparable to using a linked server from a performance perspective?
So for Azure SQL Database, are we okay with a multiple database architecture using Azure SQL Database elastic query, or, should we stick to a single Azure SQL Database and use schemas to subdivide within the single Azure SQL Database? Assume that maximum database size is not something we will run up against.
Thanks
Hello,
If elastic queries are parameterized then they will push parameterized operations to remote databases avoiding to retrieve large row sets, and will show good performance. Whenever elastic queries need to transfer large row sets you will see bad performance.
One thing you may consider is to unify all your databases into one (as you mentioned) and create a separate schema for each database. This way you will avoid the performance impact of transferring large row sets between databases.
Hope this helps.
Regards,Alberto Morillo
SQLCoffee.com
这篇关于一个Azure SQL数据库与多个的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
