|
|
Posted by Erik Lautier on 12/18/06 23:06
Erland Sommarskog wrote:
> Erik Lautier (lautier@gmail.com) writes:
> > I have a content site where everything is currently in one SQL Server
> > DB. As I add features to the site, for example message boards and
> > blogging, does it make sense to put those features in a separate
> > database? What would I lose and gain in doing so? Thanks so much.
>
> It's difficult to say without knowing more about the business as such.
> But assuming that you have common concepts like users, and you may want
> to have links between different entities, a single database makes life
> simpler. Cross-databases references are messy.
>
> But if the message board and the blogs are entirely unrelated, separate
> databases may be a better idea.
>
> One advantage of separate databases, is that if the message-board database
> crashes, the blog database may still be available.
Thanks Erland...what if the message board and blog were to sit in
subdomains - is that a stronger argument for using a different
database? My concern is that if the traffic builds, I wouldn't want
activity in one area to slow down other areas of the site; but I don't
want to sacrifice simplicity either. From the sound of it, there's no
hard and fast rule about this...I'm just trying to plan in the event I
get the traffic going. Easier to fix now than later. :)
Erik
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|