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 |
|
bjornh
Yak Posting Veteran
87 Posts |
 Posted - 2003-12-30 : 08:55:14
|
| Ello guys!after reading this article (http://www.sqlteam.com/item.asp?ItemID=1452), i thought it would be nice to split my db into 2 databases. 1 for administration (that is, client info, some error info, etc) and 1 for the rest of the project. 1 reason was so i could easly use an Access db project to do the administration from. But, there's a but (there always is...) The client table contains, clientnumbers, and those are used in db number 2. So i can't setup a relationship (not in a normal way, maybe a trigger?..) So my question is:is it usefull to split the db, i still want to use an Access Project, but i don't want the administration to be able to change or in a more proffesional way of saying, 'fuck-up' thing in the data from db 2. What is a good option?Thanks |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2003-12-30 : 11:11:23
|
| I've never been a fan of the multiple database setup. In my experience, having a single "large" database worked so much nicer for me. Having said that my databases are sub 10GB, so I've not run into some of the issues with the big single database.One question you need to ask yourself is this:What advantages do you have with putting some data in Access vs some in SQL server?What I suggest is have a single database and use access as a front-end to said data.Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
 |
|
|
smccreadie
Aged Yak Warrior
505 Posts |
Posted - 2003-12-30 : 12:42:29
|
| I occassionally use multiple databases for projects when the number of objects gets high (100s of tables, SPROCS, etc.) It helps keep things a little more organized. In one of my projects, I put all the batch operations in one database, the account administration in another, and the actual app in the third.It works pretty well for me. I've not tried splitting between sql and access though. |
|
|
|
bjornh
Yak Posting Veteran
87 Posts |
Posted - 2003-12-30 : 14:18:28
|
The ID was, an Access project (not a 'normal' access db), so access is the frontend. There still is a sql server involved. But i think i will create a new user, and give him premissions to only view the administration tables... But the article @ SQL team made me wondering, "what if" :) So problem solved. thanks and happy new year  |
|
|
|
|
|
|
|
|
1 or 2 db's?