Skip to main content

Pros/Cons Usingof using multiple databases vs using a single database

I was working on a new project which has the requirement to use 7 databases. Arguing, arguing that performance, stability, optimization is easierare more easily implemented.

While I don't agree, I'm having trouble collecting good arguments to use a single database. (While the 7 databases splitssplitting the tables ininto logical domains).

One argument I have so far is data integrity (I can't use foreign keys between databases).

What are good pros/cons for using a single or multiple databases?

[summary so far]

Arguments against multiple databases:

  • Losing data itegrityintegrity (can't use foreign keykeys over databases)

  • Losing restore integrity.

  • Gaining complexity (db userusers/roles)

  • Small odds server/database will go down.

Solutions:

  • Use schemas to seperateseparate domains.

  • POC: Use dummy data to proofprove the point in 7/1 db's execution plans

Pros/Cons Using multiple databases vs using single database

I was working on a new project which has the requirement to use 7 databases. Arguing performance, stability, optimization is easier implemented.

While I don't agree, I'm having trouble collecting good arguments to use a single database. (While the 7 databases splits the tables in logical domains)

One argument I have so far is data integrity (I can't use foreign keys between databases).

What are good pros/cons for using a single or multiple databases?

[summary so far]

Arguments:

  • Losing data itegrity (can't use foreign key over databases)

  • Losing restore integrity.

  • Gaining complexity (db user/roles)

  • Small odds server/database will go down.

Solutions:

  • Use schemas to seperate domains.

  • POC: Use dummy data to proof point in 7/1 db's execution plans

Pros/Cons of using multiple databases vs using a single database

I was working on a new project which has the requirement to use 7 databases, arguing that performance, stability, optimization are more easily implemented.

While I don't agree, I'm having trouble collecting good arguments to use a single database (splitting the tables into logical domains).

One argument I have so far is data integrity (I can't use foreign keys between databases).

What are good pros/cons for using a single or multiple databases?

[summary so far]

Arguments against multiple databases:

  • Losing data integrity (can't use foreign keys over databases)

  • Losing restore integrity

  • Gaining complexity (db users/roles)

  • Small odds server/database will go down

Solutions:

  • Use schemas to separate domains.

  • POC: Use dummy data to prove the point in 7/1 db's execution plans

Tweeted twitter.com/StackDBAs/status/1156308596830932994

WorkingI was working on a new project which has the requirement to use 7 databases. Arguing performance, stability, optimization is easier implemented.

While I don't agree, I'm having trouble collecting good arguments to use a single database. (While the 7 databases splits the tables in logical domains)

One argument I have so far is data integrity (can't usI can't use foreign keys between databases).

What are good pros/cons for using a single or multiple databases?

[summary so far]

Arguments:

  • Losing data itegrity (can't use foreign key over databases)

  • Losing restore integrity.

  • Gaining complexity (db user/roles)

  • Small odds server/database will go down.

Solutions:

  • Use schemas to seperate domains.

  • POC: Use dummy data to proof point in 7/1 db's execution plans

Working on a new project which has the requirement to use 7 databases. Arguing performance, stability, optimization is easier implemented.

While I don't agree I'm having trouble collecting good arguments to use a single database. (While the 7 databases splits the tables in logical domains)

One argument I have so far is data integrity (can't us foreign keys between databases).

What are good pros/cons for using a single or multiple databases?

[summary so far]

Arguments:

  • Losing data itegrity (can't use foreign key over databases)

  • Losing restore integrity.

  • Gaining complexity (db user/roles)

  • Small odds server/database will go down.

Solutions:

  • Use schemas to seperate domains.

  • POC: Use dummy data to proof point in 7/1 db's execution plans

I was working on a new project which has the requirement to use 7 databases. Arguing performance, stability, optimization is easier implemented.

While I don't agree, I'm having trouble collecting good arguments to use a single database. (While the 7 databases splits the tables in logical domains)

One argument I have so far is data integrity (I can't use foreign keys between databases).

What are good pros/cons for using a single or multiple databases?

[summary so far]

Arguments:

  • Losing data itegrity (can't use foreign key over databases)

  • Losing restore integrity.

  • Gaining complexity (db user/roles)

  • Small odds server/database will go down.

Solutions:

  • Use schemas to seperate domains.

  • POC: Use dummy data to proof point in 7/1 db's execution plans

Post Migrated Here from stackoverflow.com (revisions)
Source Link
rdkleine
  • 421
  • 1
  • 4
  • 7

Pros/Cons Using multiple databases vs using single database

Working on a new project which has the requirement to use 7 databases. Arguing performance, stability, optimization is easier implemented.

While I don't agree I'm having trouble collecting good arguments to use a single database. (While the 7 databases splits the tables in logical domains)

One argument I have so far is data integrity (can't us foreign keys between databases).

What are good pros/cons for using a single or multiple databases?

[summary so far]

Arguments:

  • Losing data itegrity (can't use foreign key over databases)

  • Losing restore integrity.

  • Gaining complexity (db user/roles)

  • Small odds server/database will go down.

Solutions:

  • Use schemas to seperate domains.

  • POC: Use dummy data to proof point in 7/1 db's execution plans