blocks|key|494071|text|几年前，我创建了类似的东西，使用视图和存储过程将主数据库中的数据导入到从属数据库中。这将使您能够相当容易地将这些主表连接到其他从属表中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|494072|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I created something like this a few years ago using views and stored procedures to bring in the data from the Master database into the subordinate databases. This would allow you to fairly easily join those master tables into the other subordinate tables.

blocks|key|494086|text|你调查过使用RAC吗？您可以有多个物理数据库，但只有一个逻辑数据库。这将解决你所有的诚信问题。您可以留出节点用于报告。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|494087|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Have you looked into using RAC? You can have multiple physical databases but only one logical database. This would solve all of your integrity issues. And you can set aside nodes just for reporting.

blocks|key|473974|text|给你几个网址。扩展实现可能会有很大的不同，以适应需求，但希望这些可以帮助您。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|473975|http://blogs.msdn.com/b/sqlcat/archive/2008/06/12/sql-server-scale-out.aspx|offset|length|473976|这个是以2005年为中心的，但是非常好的http://msdn.microsoft.com/en-us/library/aa479364.aspx#scaloutsql_topic4。|473977|这是一个很好的报告方法..。http://msdn.microsoft.com/en-us/library/ms345584.aspx|473978|给您一个分析服务--一个也是:)+http://sqlcat.com/whitepapers/archive/2010/06/08/scale-out-querying-for-analysis-services-with-read-only-databases.aspx|473979|entityMap|0|LINK|mutability|MUTABLE|url|1|http://msdn.microsoft.com/en-us/library/aa479364.aspx#scaloutsql_topic4|2|http://msdn.microsoft.com/en-us/library/ms345584.aspx|3|http://sqlcat.com/whitepapers/archive/2010/06/08/scale-out-querying-for-analysis-services-with-read-only-databases.aspx^0|0|0|23|0|0|K|1Z|1|0|E|1H|2|0|H|3B|3|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@$D|14|E|15|1|16]]|A|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|J|3|K|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|L|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|C]]|S|$5|O|P|Q|A|$R|T]]|U|$5|O|P|Q|A|$R|V]]|W|$5|O|P|Q|A|$R|X]]]]

A few urls for you. Scale out implementations can vary wildly to suit requirements but hopefully these can help you.

<a href="http://blogs.msdn.com/b/sqlcat/archive/2008/06/12/sql-server-scale-out.aspx" rel="nofollow">http://blogs.msdn.com/b/sqlcat/archive/2008/06/12/sql-server-scale-out.aspx</a>

this one is 2005 centric but is VERY good
<a href="http://msdn.microsoft.com/en-us/library/aa479364.aspx#scaloutsql_topic4" rel="nofollow">http://msdn.microsoft.com/en-us/library/aa479364.aspx#scaloutsql_topic4</a>

this one a good solution for reporting...
<a href="http://msdn.microsoft.com/en-us/library/ms345584.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms345584.aspx</a>

given you an analysis services one too :)
<a href="http://sqlcat.com/whitepapers/archive/2010/06/08/scale-out-querying-for-analysis-services-with-read-only-databases.aspx" rel="nofollow">http://sqlcat.com/whitepapers/archive/2010/06/08/scale-out-querying-for-analysis-services-with-read-only-databases.aspx</a>

blocks|key|473994|text|不要放弃拥有单独的应用程序和通过webservice+(esque)请求链接登录/关闭函数的想法。我见过以这种方式分开的计费/用户注册系统。虽然在非常大的范围内，这可能不是一个好主意。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|473995|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Don't throw out the idea of having separate applications and linking the logon/off functions via webservice (esque) requests. I have seen billing/user registration systems separated in this way. Though at extremely large scales, this might not be a good idea.

I am administering a rather large database that has grown in complexity and design from a single application database. Now there is a plan to add a fifth application that carries with it its own schema and specific data. I have been researching SSO solutions but that is not really what I am after. My goal is to have one point of customer registration, logins and authorization.

Ideally, each application would request authentication and be given authorization to multiple applications, where the applications would then connect to the appropriate database for operations. I do not have first hand experience dealing with this degree of separation as the one database has been churning flawlessly for years. Any best practice papers would be appreciated :)

I would envision a core database that maintained shared data - Customer/Company/Products

<ol>
<li>Core tables and primary Keys –To maintain referential integrity should I have a smaller replicated table in each “application” database. What are some ways to share keys among various databases and ensure referential integrity?</li>
<li>Replication – Two subscribers currently pull data from the production database where data is later batched into a DW solution for reporting. Am I going down a road that can lead to frustration? </li>
<li>Data integrity – How can I ensure for example that:
DATABASE_X.PREFERENCES.USER_ID =always references a= CORE_DATABASE.USERS.USER_ID</li>
<li>Reporting – What type of hurdles would I cross to replicate/transform data from multiple databases into one reporting database?</li>
<li>White Papers - Can anyone find good refernces to this strategy in practice?</li>
</ol>

Thanks

One User database servicing multiple application databases

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在管理一个相当大的数据库，该数据库的复杂性和设计都是从单个应用程序数据库中增加的。现在有一个计划添加第五个应用程序，它带有自己的模式和特定数据。我一直在研究SSO解决方案，但这并不是我真正想要的。我的目标是拥有一个点的客户注册，登录和授权。理想情况下，每个应用程序将请求身份验证，并获得对多个应用程序的授权，然后应用...

问为多个应用程序数据库提供服务的一个用户数据库
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为多个应用程序数据库提供服务的一个用户数据库EN