Chat with us on the course Piazza site if you have any questions!
We're excited to once again utilize Jupyter notebooks to allow for more
interactivity in the class. Installation instructions are available here.
Python is used in the in-class activities, homework and projects.
For the attendance portion of the class (SCPD students are exempt from this), we will write a code on the board during class. From your primary stanford email, send a note to email@example.com with the code in the Subject Line of the email. Do not write anything other than the code in the subject line and make sure that the body of the email is empty.
The reading material listed below is optional, but it refers to Database Systems: The Complete Book by Garcia-Molina, Ullman, and Widom. The lecture plan below may change.
|#||Date||Topic||Lecture Materials||Extra Reading Material||Assignments|
|Introduction and Querying|
|1||9/27||Course Logistics and Database History||
Notebook data: dataset_1.db
|Greenspun- SQL for web nerds||
|3||10/4||SQL: Advanced||Ch. 6|
|Database Design and Normal Forms|
|4||10/6||Database Design: ER Diagrams||
Project Part 1
||5||10/11||Database Design: Theory 1||
|Ch. 3.2-3.7||PS #1 Due||6||10/13||Database Design: Theory 2||
|7||10/18||Transactions from a User's Perspective||
|Ch. 8.6||Project Part 1 Due|
|8||10/20||Mechanisms for Transactions: Logging and Locking||Ch. 18.1-18.4||Midterm|
|9||10/25||Midterm Review||PS #2 Due|
Location: NVIDIA and Hewlett 200 (overflow)
|11||11/1||Guest Lecture: Hakan Hacigumus, Google Ads|
|Introduction to Database Internals|
|12||11/3||IO Cost Models and External Sort||
Project Part 2
|14||11/10||Access Methods and Operators||
|Ch. 15 (except 15.9)|
|15||11/15||Joins: A Cage Match||Ch. 2 and 16.3||
Project Part 2 Due
Project Part 3
|Ch. 2 and 16.3|
|Thanksgiving Break: 11/21-11/25|
|18||12/1||Guest Lecture: Matei Zaharia, InfoLab Faculty and Spark Cocreator||PS #3 Due|
|19||12/6||Research Talk: Dark Data and Analytics Systems||
|Wrap up and Final|
|20||12/8||Final Exam Review||Project Part 3 Due|
Unless otherwise specified in the staff section below, office hours will be held in the open area of the Huang basement. CAs will bring signs to identify themselves. Please see the staff section below for office hours.
Note: the schedule of office hours may change from time to time, in which case an announcement will be made on the course Piazza.
We encourage you to discuss the Programming Projects and Problem Sets with other students; it's fine to discuss overall strategy and collaborate with a partner or in a small group, as both giving and receiving advice will help you to learn.
However, for the Programming Projects, you must write your own code: it's not OK to share code or write code collaboratively. (This includes posting and/or sharing your code publicly, such as on GitHub!) Likewise, for the Problem Sets, you must write up your own solutions to all of the problems, and you must cite all people you worked with. If you do not do so, we will consider this a violation of the Stanford Honor Code.
If you consult any resources outside of the materials provided in class, you must cite these sources. We reserve the right to assign a penalty if your answers are substantially derivative, but, as long as you provide appropriate citations, we will not consider this an Honor Code violation.