Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
coderdude
Starting Member
24 Posts |
 Posted - 2005-11-14 : 17:13:27
|
| I have a website that allows our customers to register and log in to access some data services. It also allows for some personalization. Currently all data is stored in one database that contains the user's personal information and settings (just a couple of tables).I'm in the process of adding two other services (with more coming down the road). One is an in-depth survey which will have about 5 tables of data as well as another table for storing the user's responses. The other service is data service that has about 10 tables of data for reports, etc.My thought is that I would create a new database for each new service. This would help keep each service's tables/stored procedures isolated. i.e:DemographicsSurveysProductDataIn doing this I assume it would be better to store the user's responses in the Survey database since it is specific to that service.Also, with this set up I realize if I wanted a report of users with their survey results I would have to run a query with a join between two different databases. How does this affect performance?What are the other pro/cons for putting tables for each service in it's own database vs. keeping them all in one database?Thanks! |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-11-14 : 17:17:35
|
| I would go with one database as it requires less database maintenance to maintain. You aren't really buying anything by putting them in separate databases. You can easily isolate the objects by using a good naming convention.Tara Kizeraka tduggan |
 |
|
|
|
|
|
Database Architecture