扩展SQL Azure表/架构的体系结构要求 [英] Architecture requirements to scale SQL Azure Tables/Schemas

问题描述

我正在SQL Azure中设置架构/一些表，想知道是否需要做一些架构上的事情来提升可伸缩性，尤其是水平可伸缩性.ID应该是某种类型吗?主键是某种类型的吗?

I am setting up a schema/some tables in SQL Azure and wanted to know if there were any things i need to do architecturally in order to promote scalability, especially horizontal scalability. Should IDs be of a certain type? Primary keys be of a certain type?

我希望避免将来的风险/问题...让我知道.

I am looking to avoid risk/issues down the road... let me know.

谢谢

推荐答案

我建议您阅读文章

I would suggest you to please read the article Scale Out with SQL Database (en-US) which explains ins details about what is needed for Horizontal Partitioning of your SQL Database.

现在您还可以将SQL Federation与SQL数据库一起使用，因此向外扩展SQL Azure Federation 的帮助将帮助您确定可以在需要时进行扩展的最佳体系结构.

Now you can also use SQL Federation with SQL Database so another article on Scaling Out with SQL Azure Federation will help you to decide the best architecture which can scale out when in need.

这篇关于扩展SQL Azure表/架构的体系结构要求的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！