Different DataBases for a Single Project

•

What is DaniWeb IT Discussion Community?

You're currently browsing the Database Design section within the Web Development category of DaniWeb, a massive community of 455,865 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 3,649 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.

Join our community!

Please support our Database Design advertiser: Programming Forums

Thread Tools Display Modes

Views: 1138 | Replies: 3

Previous Post in Thread

Next Post in Thread

•

Join Date: Feb 2006

Posts: 18

Reputation: rich_m is an unknown quantity at this point

Rep Power: 3

Solved Threads: 0

rich_m

Offline

Newbie Poster

Different DataBases for a Single Project

Jul 13th, 2008

My team( all freshers) are developing a project that will involve many Modules.

I want to know if it is a good practice to have different databases for a single project!!! I know that this could lead to a bad design, if you make the wrong decisions of placing the respective tables.

Each database of a module will contain only the module specific tables (that do not need communication to the other tables of other modules), commonly used tables will be placed in a common database.

I want to know the demerits of such a design, cause junking up a database with a lot of tables, seems to be a very complicated system to understand, I mean the documentation part.

Can we relate tables in different databases????