>Hi all,
>
>Can someone please tell me the pro&cons of using one Database and all tables belonging to this Database against spliting the tables to few Databases container?
>
>Thanks.

There is one major advantage of using multiple databases: modularity. I have used multiple databases for building large systems with several modules. For example I wrote a system for a health care organization that had marketing, human resource, client records, and billing components. I utilized 5 databases:

Marketing
Employee
Client
Billing
System

This helped organize the project into modular pieces. Each module utilizes the system database for lookup tables, key field generation, security, error logs, etc. The modules are designed to stand on their own, able to be installed seperately, and be easily used in other projects. The modules never reference each others database tables directly. Instead I interface through a view stored in the modules database that points to the tables of the database that has the tables I need. For example I have views inside of my Billing database that look to tables inside of the Client database to provide information used in invoice processing.

One big beneift this gave me immediately was reducing server load and being able to increase performance. A billing server in the accounting office contains the billing database and tables. The human resource office has the employee database and tables. The client and system database is stored on a central server. In fact the executable is located on the central server but depending on which workstation it is executed from automatically makes the data for that particular department uses close by. It also helped us develop easier with multiple programmers as multiple people manipulating the same database structure is a sure way to get into trouble.

I would never recommend breaking up a database unless you are doing a large project with multiple modules however. It would just complicate things unnecessarily.

Hope this helps your decison.