From: Chad Vernon
Date: December 24 2012 3:11am
Subject: Animation studio asset management
List-Archive: http://lists.mysql.com/mysql/228841
Message-Id: <6685728441071071759@unknownmsgid>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=20cf307f380af5c1e504d1908e5c

--20cf307f380af5c1e504d1908e5c
Content-Type: text/plain; charset=ISO-8859-1

Hi there,
I'm designing an animation studio database to track assets across multiple
shows.  My original design was to have a "show" table to track which asset
belongs to which show with a show_id column.  A couple coworkers suggested
having a database per show because they are worried about performance and
reliability vs a single database as the number of shows grows.  I don't
think reliability would be different because it's all on the same MySQL
server anyways.  Is that assumption correct?  I've read a few articles
about multi-tenant database design, however the motivation for multiple
databases seems to be security which doesn't apply to us.  Am I correct in
trying to push a single database design for this?  If it helps, we have no
dedicated dba and currently a single mysql server machine.

Thanks,
Chad

--20cf307f380af5c1e504d1908e5c--