Seperate SQL Tables into Databases? 2

[ironhide1975]

Would be beneficial to seperate different web applications across different databases. Or is it better to just keep them all into one database? I can imagine that seperating the applications across different databases will require more open connections that would slow the system down.

 

[QatQat]

Even if you leave them all onto the same database, you still need to establish different connections; I do not see how it would be better, and actually it would make your different applications difficult to manage/develop/debug etc.


I would definitely keep different application on separate DB.

Cheers

QatQat

Life is what happens when you are making other plans.

 

[DotNetGnat]

separate DB for different applications...

-DNG

 

[SQLBI]

If you can, and obviously depending on the resources used by each one, use a seperate server for each app.



Cheers,
Leigh

Sure, if it has a microchip in it, it must be IT... Now what seems to be the problem with your toaster...?

 

[ironhide1975]

SO keeping them in one database wouldn't be easier to debug?

 

[DotNetGnat]

No...

-DNG

 

[QatQat]

it can make your life a misery, just think only of users' management; by keeping all apps onto one database you have to use table level users, instead, new app, new database, new user, much easier also if you intend giving other users admin rights over their application.


Cheers

QatQat

Life is what happens when you are making other plans.

 

[Tarwn]

Applicaiton maintenance is actualy easier fthe databases are split up as well. Rather than trying to sort through the list of tables, stored procs, etc just to figure out which ones belong to a specific application, you will already know that everything in the database is directly relevant to the application your working on. Additionally, you will have less chance of accidentally tying into another applications table as QatQat was pointing out.

However, if you have two or three applications that are working in concert on a larger thing, then sometimes it is better to group them. For instance, I have been working on tracking usage for a set of 20 mdb files that predated me. Trying to figure out who has copies of the files on their system, which formstey open, etc. So I have a login script that finds the files and reports them to two tables in a database, but then I also have some VBA code in the MDB files that report to the same database each tme a form is opened. Technically differant applications, but it made sense to group these since they are working on the same general project and will be duplicating machine and file data.