Location visible to members
This meetup's topic is David Berube talking about "Improving Your Database Designs with Practical Database Theory".
Today, many programmers have a skillset focused on the application layer - ORM systems like Hibernate and Ruby on Rails can hide much of the complexity of SQL programming, so many feel that focusing on their database is unimportant. ORMs, of course, have brought many benefits - but their widespread use has also resulted in many programmers being less familiar with the theoretical underpinings of their database system; they focus on their application, not on the database. Still, database design is important, and is often neglected. In many organizations, developers are often left on their own to develop an appropriate schema - and this talk will present a brief, background in database theory, teaching the listener to make designs which are practical and based on solid experience. This talk, though, won't teach you to pass a computer science exam - it's not a dry, theoretical lecture, but instead a practical exploration of fundamental issues in database design and how they effect real world applications. For example, the fundamental nature of a table, a row, and a column will be explained in simple, practical terms - and the listener will be shown what this means for your database design. Short, easy to remember rules and explanations will be given. Proper database design can give you confidence that your data is accurately and concisely represented - resulting in performance and reliability benefits. The process of database normalization is an important part of this. Instead of classroom definitions, this talk will cover some handy "rules of thumb" for normalization - honed from many years of practical experience. Such rules explain both how to detect errors and how to correct them. Of course, sometimes the benefits outweigh the cost, so the the listener will be taught how to discern when it's best to leave an imperfect design as it is. Finally, a short selection of common errors in database design will be discussed, each with an explanation of why it poses a danger, and how to fix it - even if you've already stored large quantities of data in that flawed design.
------------- Logistics -------------
MIT's map with the building (E51) highlighted: http://whereis.mit.edu/map-jpg?selection=E5... (http://whereis.mit.edu/map-jpg?selection=E51&Buildings=go)
MIT's map with the Kendall square T stop highlighted: http://whereis.mit.edu/map-jpg?selection=L5... (http://whereis.mit.edu/map-jpg?selection=L5&Landmarks=go) (the stop is in red on that map, and you can see E51 in the bottom right)
MIT's maps with parking lot information: http://whereis.mit.edu/map-jpg?selection=P4... (http://whereis.mit.edu/map-jpg?selection=P4&Parking=go) and http://whereis.mit.edu/map-jpg?selection=P5... (http://whereis.mit.edu/map-jpg?selection=P5&Parking=go)
Note that MIT lots are free to park in after 3 pm or so, even if it says "reserved for faculty"
Free pizza and soda will be served, so please RSVP accurately.
To RSVP anonymously, please login to the Meetup site with the e-mail address "admin at sheeri dot com" and the password "guest". For more information, see: http://www.meetup.com/mysqlbos/calendar/