gt;
> Please do not alter or otherwise disrupt this transmission.
>
>
>
> > Date: Sun, 23 Dec 2012 22:39:01 -0800
> > Subject: Re: Animation studio asset management
> > From: chadver...@gmail.com
> > To: mich...@j3ksolutions.com
> > CC: mysql@lists.mysql.com
f=false
Boxing Day is December 26thMartin Gainty
__
Please do not alter or otherwise disrupt this transmission.
> Date: Sun, 23 Dec 2012 22:39:01 -0800
> Subject: Re: Animation studio asset management
> From: chadver...@gmail.com
> To: mic
Thank you for the responses.
The database would only be accessed internally by about 30-60 users max.
An average show could add anywhere from 5,000-20,000 records over a period
of a few months. We would do maybe 3-4 shows a year.
Maybe a few dozen records would be inserted daily, updates would no
In the last episode (Dec 23), Chad Vernon said:
> 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
Database performance (like system performance) is always driven by a
give and take process, a trade-off between resources (this includes
design expertise) available, and the required results.
How many records are you dealing with?
How often are records are being added and/or updated?
How many u
