Viewing 9 posts - 586 through 595 (of 595 total)
I agree that the single database may be easier to set up and maintain, however, Antares686 does address some points regarding multiple database architecture which I have found very compelling...
December 20, 2002 at 7:18 am
quote:
Another downside to splitting - if you're using transactions that span two or more db's and then need to recover one...what fun!
December 4, 2002 at 9:37 am
quote:
What's your primary goal for splitting up your database? Is it for performance wise?
No, actually,...
November 25, 2002 at 6:16 am
quote:
BTW, any other opinions from the opposite side?
Don't know if you're done with this topic,...
November 21, 2002 at 7:35 am
Actually, you can change the default to be NOT NULL. It is in BOL:
quote:
If any database settings are configured (changed with...
November 8, 2002 at 8:05 am
I completely understand the walking and chewing gum dilemma. So, to sum up then, you believe it is better to have commonly shared data stored in a separate database,...
November 8, 2002 at 7:31 am
Point b) has been answered. Thank you.
As for point a) , yes, I was referring to a PK_ to FK_ relationship. I would have to use a trigger...
November 7, 2002 at 3:12 pm
Actually, we are in a situation now in which we have multiple databases, however, I was under the impression that one could not enforce a CONSTRAINT across multiple databases. ...
November 7, 2002 at 2:56 pm
quote:
This is a valid point, but I feel one that adds too much overhead to application development to deal with. I...
November 7, 2002 at 7:59 am
Viewing 9 posts - 586 through 595 (of 595 total)