Results 1 to 8 of 8
  1. #1
    Join Date
    Feb 2014
    Posts
    2

    Unanswered: Multiple Database Vs Single Database for departments in organisation

    I'm working with environmental organisation We have 8 departments (SOil, AIr, Water, Marine ..... ) and within every department we have one or multiple projects. Some projects have already started and some are planned for future.

    We have already one project in place and its mandate is to Build and maintain a comprehensive environmental database for all departments. As of now most of the data from all departments are stored in this centralized database. Since every department in organisation are trying to create/collect new type of data regarding environment.Some Of the data (Existing or going to be created in new projects) among the departments are common and there is some data that is department or project specific.

    But as I said if we allow to create everyone their own database for their project it will be complete chaos. We will land in having many databases and there will be high chances data will get repeated may be within same department ( as their may be multiple projects with one departments) and also within organisation.

    What are the Pros and Cons of allowing them to create separate database?
    Is this better to ask them to have only one database or allow them to create their own but please note their are multiple department and they have started different projects.
    One Departments accesses data from other departments through (provided he has privilege) web application which is used by all departments for their daily tasks.

  2. #2
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    One database is almost certainly the correct answer.

    Without knowing a great deal more about how the data will be used, shared, etc. there are too many ways for me to pick just one on how to manage their data.

    -PatP
    In theory, theory and practice are identical. In practice, theory and practice are unrelated.

  3. #3
    Join Date
    Jan 2013
    Posts
    354
    Provided Answers: 1
    A man with 8 wristwatches is never sure what time it is

  4. #4
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Exactly!

    -PatP
    In theory, theory and practice are identical. In practice, theory and practice are unrelated.

  5. #5
    Join Date
    Feb 2014
    Posts
    2

    Multiple Database Vs Single Database for departments in organisation

    Will there be any impact on performance?

  6. #6
    Join Date
    Feb 2013
    Location
    perth australia
    Posts
    24
    just be careful about collation. Each app is designed with a specific database collation and sometimes they make use of system databases ( e.g. temp ) and expect them to be the same collation. The app will fail when your user databases are different collation from the system databases.

  7. #7
    Join Date
    Nov 2004
    Location
    on the wrong server
    Posts
    8,835
    Provided Answers: 6
    Quote Originally Posted by shafi_trumboo View Post
    Will there be any impact on performance?
    not if you design it right with the ability to scale and then provision adequate hardware, and then monitor your system and code performance as your database and user base grows.
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

  8. #8
    Join Date
    Sep 2001
    Location
    Chicago, Illinois, USA
    Posts
    601
    In my younger years I designed a large-scale system based upon individual databases for each department. By the time we merged the DBS into a single db the company had grow to over 75 departments and the headaches involved in maintaining and upgrading 75 DBS was overwhelming. But even if you only have eight departments, a single db is the way to go. I was also worried about performance but it was absolutely not an issue.

Tags for this Thread

Posting Permissions

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