|
Home > Archive > MS SQL Data Warehousing > November 2006 > Reducing Tables Associations by Using Web Services
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Reducing Tables Associations by Using Web Services
|
|
|
| Hi folks,
First,let me use a busniness and solution model - car insurance to
present the issue
* There are 3 web services - policy, claim, pay. Each services access
their own set of database tables. The 3 table sets are isolated.
* The client application accesses 3 web services, using policy id, claim
id, check number. The client is the hub.
If this works, it apparently simplify the assocation of databasetable
tables. The question is that this style make any sense. Please advise.
Thanks.
Peter
| |
| Robert Klemme 2006-11-23, 5:16 am |
| On 21.11.2006 14:47, Peter wrote:
> Hi folks,
> First,let me use a busniness and solution model - car insurance to
> present the issue
> * There are 3 web services - policy, claim, pay. Each services access
> their own set of database tables. The 3 table sets are isolated.
> * The client application accesses 3 web services, using policy id, claim
> id, check number. The client is the hub.
> If this works, it apparently simplify the assocation of databasetable
> tables. The question is that this style make any sense. Please advise.
First, I'm not sure this is actually a DWH question. Then, I would
definitively prefer to have related tables in the same schema - so the
DB can ensure consistency (FK) etc. OTOH, if the data is *completely
unrelated* then, yes, this can be a proper way to modularize.
Regards
robert
F'UP to microsoft.public.sqlserver.programming
|
|
|
|
|