一个用于处理多个应用程序数据库的用 [英] One User database servicing multiple application databases

查看:145
本文介绍了一个用于处理多个应用程序数据库的用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我管理的是一个相当大的数据库,它在单个应用程序数据库中的复杂性和设计。现在有一个计划,添加第五个应用程序,它带有自己的模式和特定的数据。我一直在研究SSO解决方案,但这不是我真正的后果。我的目标是拥有一个客户注册,登录和授权点。

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


  1. 核心表和主键 - 为了保持参照完整性,我应该在每个应用程序数据库中有一个较小的复制表。

  1. 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?

复制 - 两个订阅者目前从生产中提取数据数据库,其中数据以后被分组到用于报告的DW解决方案中。我要走下一条可能导致挫折的道路吗?

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?

数据完整性 - 如何确保例如:
DATABASE_X.PREFERENCES.USER_ID =始终引用a = CORE_DATABASE.USERS.USER_ID

Data integrity – How can I ensure for example that: DATABASE_X.PREFERENCES.USER_ID =always references a= CORE_DATABASE.USERS.USER_ID

报告 - 我将跨越多种数据库复制/数据库?

Reporting – What type of hurdles would I cross to replicate/transform data from multiple databases into one reporting database?

白皮书 - 任何人都可以在实践中找到良好的推荐策略?

White Papers - Can anyone find good refernces to this strategy in practice?

感谢

推荐答案

横向扩展的实现可以根据需要大幅变化,但希望这些可以帮助您。

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

http://blogs.msdn.com/b/sqlcat/archive/2008/06/12/sql-server- scale-out.aspx

这一个是以2005年为中心,但非常好
http://msdn.microsoft.com/en-us/library/aa479364.aspx#scaloutsql_topic4

this one is 2005 centric but is VERY good http://msdn.microsoft.com/en-us/library/aa479364.aspx#scaloutsql_topic4

这是一个很好的解决方案报告...
http://msdn.microsoft.com/en-us/library/ms345584.aspx

this one a good solution for reporting... http://msdn.microsoft.com/en-us/library/ms345584.aspx

给您一个分析服务:)
http://sqlcat.com/whitepapers/archive/2010/06/08/scale-out-querying-for-analysis-services-with-read-only-databases.aspx

given you an analysis services one too :) http://sqlcat.com/whitepapers/archive/2010/06/08/scale-out-querying-for-analysis-services-with-read-only-databases.aspx

这篇关于一个用于处理多个应用程序数据库的用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆