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 |
sasan.kh
Starting Member
23 Posts |
Posted - 2007-05-18 : 07:29:32
|
Hi AllI have a question about having one or multiple databases for a large project. What are the main differences between designing my database as one or breaking in to multiple databases. I should mention that there are many relationships between tables in different DBs in the multiple DBs state?regardssasan |
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-05-18 : 09:32:35
|
choose one db.cross db relationships aren't supported in sql.there are 3rd party tools that provide this but i'd go for a single db design._______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenp |
 |
|
mr_mist
Grunnio
1870 Posts |
Posted - 2007-05-18 : 09:55:15
|
Yep. Use one DB with multiple tables if needed. If it's too large, consider an archive and/or reporting db.-------Moo. :) |
 |
|
sasan.kh
Starting Member
23 Posts |
Posted - 2007-05-18 : 11:59:55
|
I know that we can have joins on different tables in multiple databases in SQl server 2000. In this manner are there any overhead on the dbms and should we spend more resources?sasan |
 |
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-05-18 : 12:08:56
|
yes there is overhead.what kind of resources?_______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenp |
 |
|
sasan.kh
Starting Member
23 Posts |
Posted - 2007-05-18 : 12:46:09
|
[quote]Originally posted by spirit1 yes there is overhead.what kind of resources?I mean system performance generally |
 |
|
|
|
|