Reducing Tables Associations by Using Web Services

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Peter - 21 Nov 2006 13:47 GMT

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

Reply to this Message

Robert Klemme - 23 Nov 2006 09:37 GMT

> Hi folks,
> First,let me use a busniness and solution model - car insurance to
[quoted text clipped - 5 lines]
> 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

Reply to this Message