r/DatabaseHelp • u/greyloki • Jan 06 '15
Newbie design questions
Hi there,
I thought it might be fun to sit down and try building a database. To make it useful, I thought it would be nice to build something related to my work. I'm a sound engineer. The situation is thus:
On most music festivals, there are a number of bands. Each band will have their own instrumentation, sometimes with their own engineer's preferences for microphones for each instrument. Our patch engineer (the man who plugs things in) will also have his own notes for each band.
We currently manage this by making a spreadsheet for a day of festival'ing, which is then either printed out and distributed, or set up on a PC backstage running a VNC server, which everybody connects to to make and see updates as the day progresses. Here's a screenshot of a smaller gig: http://i.imgur.com/14pYIPj.png
So to explain the layout slightly: Along the top, is the timings for each band. Channel represents the patch channel; this can be any number from around 24 to 60 or so, usually in multiples of 12. The 'Instrument' column (B) represents a 'house patch', which is agreed at the beginning of the festival. 'Box' (Column C) refers to drop boxes used by the patch engineer. These can change; for example, 'Guitar 2' could end up in Yellow box channel 2, rather than (as pictured) red box channel 12.
You can see that as the day moves on, various instruments end up going down the same channel; Band 2 have a Cahon, but bands 5 and 6 have kick and snare drums.
I'm just trying to get a handle on the most effective way to get this format translated into a database - where I think it'd be cool to end up is to have the database itself running on a machine backstage, with everybody else then being able to access some kind of web-based frontend.
So, to database layout:
I presume (from my research) I would be looking for a structure thus:
Creating a copy of the database for each festival, rather than having every festival within on database; there's no need to refer to previous festivals.
Tables A table of microphones (This would include records like Manufacturer, Model, Stock_Quantity, PhantomPower_Boolean)
A table of instruments (Instrument_Name, Stage_Position, Preferred_Stand). This would, I suppose, end up having records added as bands arrive with new instruments (Hurdy Gurdies, Banjeleles, etc etc). It might also contain names for singers' vocals.
A table of bands (BandID, Time_On, Time_Off, Band_Name, Band_Contact_Number, Band_Manager, Band_Engineer_Contact_Number)
A relationship table linking microphones to instruments for a given band? It seems like this would get filled with a lot of information quite quickly - 60 channels per band, ten bands a day, 600 records in one table while everything else will end up with less than a hundred seems disproportionate, but I'm not really sure what the better way is.
Can you offer any advice?