最佳实践ASP.NET成员：在同一数据存储用户表？ [英] Best Practice ASP.NET Membership: User tables in the same datastore?

问题描述

它是更好地与ASP.NET成员安全模型的表致以业务数据库。或者我应该有一个不同的数据存储在哪里，我只管理身份与角色...基本上1个或2个数据库？

Is it better to extend my business database with the tables of the ASP.NET Membership Security model. Or should I have a different datastore where I only manage Identities and Roles... Basically 1 or 2 databases?

推荐答案

这可能取决于规模。如果它是一个企业解决方案与不同的应用程序共享一个成员来源，答案很简单 - 将它们分开。也可能有表现的原因，你会想这个数据从应用程序的其余部分分开。可以说这些表不例如数据仓库属于。

This can depend on scale. If it's an enterprise solution with different apps sharing one membership source the answer is simple - separate them. There might also be performance reasons why you would want to separate this data from the rest of the app. Arguably these tables do not belong in a data warehouse for example.

2的数据库解决方案不会给你的唯一事情是参照完整性。如果您延长您的会员表来保存有关用户更多的应用的具体细节，而这些表需要链接到主数据库，那么你可能要保持他们在一起。否则，你将需要某种形式的复制作业的维护这个给你。

The only thing the 2 databases solution doesn't give you is referential integrity. If you extend your membership tables to hold more application specific details about the user, and these tables need to link into the main database then you might want to keep them together. Otherwise you would need some sort of replication job maintaining this for you.

这篇关于最佳实践ASP.NET成员：在同一数据存储用户表？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！