Hi,
I'm trying to solve an interesting problem in my persistance layer, DB
connection
pooling.
Issue:
- We have many physical DB's, segmented by city. Same schema at each
location.
- An SQL statement: select row, row from customer where cust_id='some
location's customer';
How can this SQL be routed to the correct DB connection (physical DB)
based on:
- table
- value of the select by columns and values
(horizontal table segmentation)
- I don't want my business logic to worry about grabbing the correct DB
connection based on
range of primary keys, table names etc etc!!!!
Possible solution:
- This is an age old decission support big DB problem that various
persistence layer
products and tools have been developed to solve
- The data warehousing problem also looks like what our segmented physical
DB arch. would
look like.
- Find a persistance layer that works with Appserver ABC that does table and
key ranges routing
to the correct physical DB.
- All DB connections in the Appserver's pool are equal and will work
regardless of the table,
primary key value, etc you are accessing.
Anyone have comment or products that may help with this?
Thanks.
curt
Curt Smith
Z-Tel, Architect
email: [EMAIL PROTECTED]
work: 404-237-1166 x182
FAX: 404-237-1167
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
