Skip to main content
Database Administrators

Return to Question

Post Closed as "exact duplicate" by gbn, Mat, ypercubeᵀᴹ, Jon Seigel, Aaron Bertrand
added 1 characters in body; edited tags; edited title
Source Link
Mat
Mat
  • 10.2k
  • 4
  • 43
  • 40

Database Architecture: Which is better: one database per application, or just one database?

I ask this specifically for SQL Server, the advantages that I can see for multiple databases are:

  1. Logs are smaller (so one runaway transaction cannot cause others (replication etc) to stall)
  2. A page corruption does not affect multiple applications (can this be isolated using filegroups?)

I can't seem to find any benefits from a single database architecture (maybe the code management is simpler).

Which architecture did you choose and why?

Database Architecture: Which is better one database per application, or just one database?

I ask this specifically for SQL Server, the advantages that I can see for multiple databases are:

  1. Logs are smaller (so one runaway transaction cannot cause others (replication etc) to stall)
  2. A page corruption does not affect multiple applications (can this be isolated using filegroups?)

I can't seem to find any benefits from a single database architecture (maybe the code management is simpler)

Which architecture did you choose and why?

Which is better: one database per application, or just one database?

I ask this specifically for SQL Server, the advantages that I can see for multiple databases are:

  1. Logs are smaller (so one runaway transaction cannot cause others (replication etc) to stall)
  2. A page corruption does not affect multiple applications (can this be isolated using filegroups?)

I can't seem to find any benefits from a single database architecture (maybe the code management is simpler).

Which architecture did you choose and why?

Source Link
WrinkleFree
WrinkleFree
  • 1.1k
  • 9
  • 22

Database Architecture: Which is better one database per application, or just one database?

I ask this specifically for SQL Server, the advantages that I can see for multiple databases are:

  1. Logs are smaller (so one runaway transaction cannot cause others (replication etc) to stall)
  2. A page corruption does not affect multiple applications (can this be isolated using filegroups?)

I can't seem to find any benefits from a single database architecture (maybe the code management is simpler)

Which architecture did you choose and why?