Creating a new DB vs. Creating a new table??

Hey all,

Does anyone know of information regarding best practices in MS SQL for when to create a whole new database vs. when to create a new table? I'm working at a new job and I'm used to an enviornment where we created a database for each new database-driven tool. I enjoyed the organization that model provided, however, my new boss is worried about performance problems that could be generated by having multiple databases. He's especially worried with people using Crystal Reports who would likely just build straight joins between databases. The current situation is one database housing several hundred tables (which to me is a disaster).

Any help or suggestions would be appreciated!

Hey yutlin! I think, and it's just my opinion, that each DB should consist of several tables that hold certain relation between them. You should do a little studying about your tables and see what are the tables that have more interaction between them and form subgroups. If a subgroup is big enough, you can set it up in a separated DB.

Hope it helps! (I'd love to help you any further, but I'm not a DBA, just a programmer)

ANibal.