Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

im working with four app servers and two database instances (3DNS and BigIP determine what app server a user is directed to based on usage etc). Two app servers per database node. The database instances stay synchronized using replication.

However, when a new user first visits the application it uses SSO to get a their identification and automatically registers that user. This is a problem if say the user opens two browser at the same time , both pointing to my application. The app will try to register the user on both databases, then when replication runs it will throw a unique constraint exception.

Is there any way to manage database access in this type of architecture so that certain tables, like user registration, can only be accessed if a flag has been obtained?

thanks, any suggestions would be helpful.

share|improve this question
up vote 0 down vote accepted

Yes, with row-level locking, however I am not sure if this question is appropriate for SF or should be moved to SO? Seems like an app architecture thing, regardless of the underlying setup and/or hardware.

share|improve this answer
cheers will move – cduggan Nov 16 '10 at 17:29

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.