From: kennedy-down_with_spammers@no_spam.comcast.net   
      
   No, move all the data to 1 machine and have 3 schemas.  Then you can create   
   a view that joins the 3 schemas(1 view for each table).  The entity bean   
   approach is a Java programmer with a hammer that thinks everything is a   
   nail.]   
   Jim   
      
   --   
   Replace part of the email address: kennedy-down_with_spammers@attbi.com   
   with family.  Remove the negative part, keep the minus sign.  You can figure   
   it out.   
   "J Goldman"  wrote in message   
   news:3f69d03f$1@usenet01.boi.hp.com...   
   > Well, thanks for the vote of confidence.  I appreciate your point that   
   > this approach doesn't seem doomed to success.  With that in mind,   
   > can you offer any contructive suggestion on how I might provide   
   > global access to this data?  My other main thought has been to create   
   > a set of entity EJBs local to each machine, along with a set of global   
   > session beans.  The global session beans would use something like a   
   > dbhost parameter (where appropriate) to guide which db should be   
   > read.  Generic requests would query all of the DBs.   
   >   
   > Jason   
   > jason@fc.hp.com   
   >   
   >   
   > "Sybrand Bakker"  wrote in message   
   > news:a20d28ee.0309180357.54887fa3@posting.google.com...   
   > > "J Goldman"  wrote in message   
   > news:<3f68c63a$1@usenet01.boi.hp.com>...   
   > > > A pointer in the right direction would be greatly appreciated.   
   > > >   
   > > > Jason   
   > > > jason@fc.hp.com   
   > >   
   > > > I would like to set up a distributed database system with location   
   > > > transparency and a shared schema (i.e. horizontal fragmentation).   
   I'll   
   > > > provide a little more context:  I have three databases, running on   
   > separate   
   > > > systems, all of which use the identical schema.  So, each has entries   
   in   
   > a   
   > > > table "foo", which are unique.  I'd like to provide a global access to   
   > this   
   > > > data, so a client can effectively query the set of databases.  So,   
   > asking   
   > > > for all entries in the "foo" table would retrieve the contents of   
   > db1.foo,   
   > > > db2.foo, and db3.foo.  Ideally, when all is said and done, I'm   
   planning   
   > to   
   > > > wrap this in an enterprise java bean to provide an object interface.   
   > > >   
   > > Your scenario has 'DISASTER AHEAD' inscribed all over it. You would be   
   > > better off by using a few 1000 of voting machines using punchcards.   
   > > Your approach would require to use UNIONs for everything, which means   
   > > the database will resort to full table scan and sorting for ALL sql   
   > > you sunmit.   
   > > Need I say more? Why do you want this? Are you up for a career move,   
   > > or do you like getting sacked by HP?   
   > >   
   > > Sybrand Bakker   
   > > Senior Oracle DBA   
   >   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)