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
Dec 23
Michael Anderson Re: Animation studio asset management
Dec 23, 2012; 23:14
Michael Anderson
Re: Animation studio asset management
Dec 23
Dan Nelson Re: Animation studio asset management
Dec 23, 2012; 23:24
Dan Nelson
Re: Animation studio asset management
Dec 23
Chad Vernon Re: Animation studio asset management
Dec 23, 2012; 22:39
Chad Vernon
Re: Animation studio asset management
Dec 24
Martin Gainty RE: Animation studio asset management
Dec 24, 2012; 08:14
Martin Gainty
RE: Animation studio asset management
Jan 02
Chad Vernon Re: Animation studio asset management
Jan 02, 2013; 09:40
Chad Vernon
Re: Animation studio asset management
Search
Lasso Programming
This site manages and broadcasts several email lists pertaining to Lasso Programming and technologies related and used by Lasso developers. Sign up today!