We help IT Professionals succeed at work.
Get Started

Single Large vs. Multiple Small SQL Databases

652 Views
1 Endorsement
Last Modified: 2012-05-09
We are developing an on-line database application for tracking Athletic Data.I estimate the average customer will have 500 Athletes, 2,000 Injuries and 10,000 Treatments.

Customer
   +---- > Athletes
       +---- > Injuries
           +------ > Treatments

The advantage to a single SQL datababse would be:

1. One schema to maintain.
2. Ability for customers to compute collaborative statistics.

The downside would be:

1. Individual customer Queries are against the complete database.
2. Multiple customers accessing the same database concurrently.

The total number of records, even over 500 customers is small compared to SQL's capabilities, so I would expect a single database to be best. What are the considerations for creating a single large vs. multlple seperate (one per customer) databases of the same schema? My primary concern is querry speed.
Comment
Watch Question
Commented:
This problem has been solved!
Unlock 1 Answer and 6 Comments.
See Answer
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE