Results 1 to 8 of 8
  1. #1
    Join Date
    Jul 2010
    Posts
    6

    Advice needed. Need a database middleware?

    Hi, would like you guys' advice. Let's say we have system A, system B and system C and each system has its own user management module/tables. Meaning system A's user management module is at database A, system B's user management is at database B and system C's user management is at database C.

    Now, we plan to centralized user management module by creating a separate database, say database D and to have system A, B and C to use user management in database D. Once successfully, those user management tables in database A, B and C will be removed.

    In this design, do we need some kind of database middleware for system A, B and C to connect to database D. Secondly is what if system B need to add a special field in a user management tables in database D?

  2. #2
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,569
    You could replicate the data to the disparate databases.
    This would probably be best, as in the event of the network breaking down each database would still maintain a copy of the latest available user settings, and could continue functioning.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  3. #3
    Join Date
    Jul 2010
    Posts
    6
    hi thanks for the reply. actually reliability is not so much of our concern now. What we concern more is the design. Just like what I mentioned earlier, if system B needed extra field from the database, how do we go about it if we got once centralized database for all 3 systems?

  4. #4
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,569
    Quote Originally Posted by ngaisteve View Post
    actually reliability is not so much of our concern now.
    First WTF of 2013.
    Regardless, Replication is still probably the best solution for you. You can set up separate replication packages for each client database, if necessary, and replication can be configured at the column level.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  5. #5
    Join Date
    Jan 2013
    Location
    Woodland Hills, CA
    Posts
    18
    I agree with blindman. Irrespective of whether you're in the design phase or the development phase (looks like you guys are still in design phase), reliability should always be at the forefront of your solution. If it's not reliable then can you really trust the data that you're seeing?

  6. #6
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,569
    Quote Originally Posted by YesAgile View Post
    I agree with blindman.
    You're going to fit in well here.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  7. #7
    Join Date
    Jan 2013
    Location
    Woodland Hills, CA
    Posts
    18
    hahaha!

  8. #8
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,569
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •