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 |
|
coosey17
Starting Member
1 Post |
Posted - 2003-02-21 : 08:56:33
|
| I am currently building an online system (inventory, customers, orders, email marketing, web log analysis). I have a web server and a database server running SQL2000. I think I could put all of these things together in one database but I am not sure of the benefits. Anybody that can help I would really appreciate it...Edited by - merkin on 02/21/2003 09:35:01 |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2003-02-21 : 09:35:23
|
| Moved to a more appropriate forum.Damian |
 |
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2003-02-21 : 09:47:20
|
| Put these all in one database so that you can use foreign key constraints to enforce dri.Jay White{0} |
 |
|
|
smccreadie
Aged Yak Warrior
505 Posts |
Posted - 2003-02-24 : 06:00:01
|
| I would put stuff that is logically related in one db (inventory, customers, orders) and consider putting the rest separately. I personally find it harder to maintain a system when the table and stored procedure count gets up there (>100). Unfortunately, there's no way (outside of good naming) to organize these into folders or other classifications.My $0.02 only. |
 |
|
|
|
|
|