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 |
|
Forget_About_It
Starting Member
11 Posts |
 Posted - 2003-04-29 : 10:16:59
|
| Were currenlty looking to migrate our 10 large databases to SQL, however someone advise us that it would be earier to move then into one database in SQL rather then have them on sepearate databases. Now almost all of these databases link to each other, reading other tables and field names when pulling down a query. What I need to know is it better having them in one database or separte (which I imagine it to be way better). Separate or one? And if seperate how do you relate the databases and tables?The reason I'm asking this, the person used to work in a SQL environment, however I question what they are doing. SQL is something new to me and everyone here, so I want to do it right the first time. |
|
|
ValterBorges
Master Smack Fu Yak Hacker
1429 Posts |
Posted - 2003-04-29 : 10:56:42
|
| If the tables are related I would likely go with 1 database.http://www.sqlteam.com/item.asp?ItemID=751http://www.sqlteam.com/item.asp?ItemID=1452http://www.sqlteam.com/item.asp?ItemID=591Although it still depends on what you're trying to accomplish with the databases.If you were to go with separate databases all you tsql would have to use the following convention to address objects.database.owner.objectthe full address is server.database.owner.objectEdited by - ValterBorges on 04/29/2003 10:58:25 |
 |
|
|
simondeutsch
Aged Yak Warrior
547 Posts |
Posted - 2003-04-29 : 10:59:30
|
| And if you have relationships across separate databases, it's hard to maintain data integrity. You cannot use DRI constraints, but have to use triggers to cross-reference databases. This can be a royal pain.Sarah Berger MCSD |
|
|
|
|
|
|
Databases in one or separate