Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Multiple database vs. single database.

Status
Not open for further replies.

Albion

IS-IT--Management
Aug 8, 2000
517
US
I have a few Access databases that I am converting over to SQL. What would be more beneficial; to create an individual database in SQL for each of these database or to create one company wide database and just add all the tables from each individual access database?

thanks

-al
 
Probably the 2nd but without a lot more detail, its kind of hard to say. Why where they broken into separate databases in the first place? For example.
 
The answer really depends on the relationship between the databases. If one is for Personnel, another for Payroll, and another for Sales and Inventory, one could make a valid argument for combining the first 2 DBs into 1. The Sales and Inventory database has a different purpose and perhaps a different set of users and should probably remain separate DB even in SQL Server.

In general, I would try to keep related data together.

If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top