one database many?


i am building website control information churned entities. information common between entities, nonetheless competence owned same customer. fan competence wish control entities unparalleled "dashboard". should i have database everything, keep information seperated sole databases?
is there best-practice? positives/negatives carrying a:




  • database whole site (entity
    has "customerid", information has
    "entityid")

  • database each
    customer (data "entityid")

  • database any entity (relation of
    database fan outmost of
    database)



multiple databases seems have improved opening (fewer rows joins) nonetheless competence eventually spin maintain nightmare.



Comments

Popular posts from this blog

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?

grails record upload problems

how i emanate permitted url asp.net mvc?