distributed databases (i think)

[cynaptic]

database architecture, any good resources?

I have a project where I am consolidating several databases into one. there is much territorial p**sing going on about 'messing with my database' and 'losing functionality' etc etc. wondered if it is possible to run several different 'front ends' from one main database, as this would solve a few problems. perception is reality and if they all think that I have built the database to their own dept spec - then all of them should be happy even though they are all looking at effectively the same database.

not used to dealing with this kind of issue so help /advice much appreciated.

Thanks

 

[JimHorton]

cyn,
It's quite possible and fairly common. It works better if the same person designs all front ends, so the business rules are in sync. But, as you say, the end users need not know. You need to deal with concurrency issues in each front end, however, and this adds some logic, though no more than in any multi-user db, it's just that you have to do it in all the different front-ends, instead of just once for a shared front-end.
--Jim

 

[paron]

I've found that much "empire-building" happens because of weak division of responsibility in the organization. "I have to maintain my own list of employees because Personnel never updates their db." or "The engineers never think about the purchasing dept. when they put projects in the computer." Probably true, but . . .

How's your support at the upper echelon? Or, are you a good schmoozer yourself? (I am definitely NOT, but I admire people who are.) I am mostly reduced to making sympathetic noises and setting up the security to reflect people's assigned responsibilities. I always end up needing someone higher-connected or more personable to "front" for me? Who is championing your project? Can they help?

Also, it may help to demonstrate how security provisions mean that other departments CAN'T get into "their database" and mess their things up. Are the functional workgroups well-defined enough for that?

Implementing MichaelRed's "Poor Man's Transaction Log" (see FAQs) may reassure them that you will know "who shot John", and talking about the ability to go back to previous backed-up states may help, too.

Ron

PS -- all questions purely rhetorical, of course. Wouldn't know what to do with the answers if you gave them! Just thought-starters.

R.

 

[cynaptic]

Guys thanks for your thoughts, the chain of command seems to rather fluid, who ever is nearest to me and has not got much else to do - generally throws in their 2 cents.

In all I thinl that this must be the way forward, any resources you can think of to help with planning such sysyem.

cheers