Throughout this course, I gained a comprehensive understanding of how modern database systems are designed, implemented, and managed. The three most important concepts I learned were relational database design, SQL and query optimization, and the contrast between relational and NoSQL systems. Relational Database Design and NormalizationOne of the most valuable lessons was learning how to […]

This week, I studied the similarities and differences between MongoDB and MySQL, two widely used database management systems that represent distinct approaches to data organization. While both are designed to store, retrieve, and manage information efficiently, their underlying data models and use cases vary significantly. Understanding these differences provides valuable insight into how database design

This week, I compared two different SQL database schemas designed to manage a prescription system. Both versions handled similar entities — doctors, patients, drugs, pharmacies, prescriptions, and refills — but they differed in structure, naming conventions, and design philosophy. Through this comparison, I gained a deeper understanding of how database design choices impact readability, normalization,

Course ReflectionAt the halfway point of this course, I have developed a much deeper understanding of how relational databases work—from conceptual design to physical storage and performance optimization. The progression from SQL fundamentals to more advanced topics like indexes and normalization has clarified how databases balance structure, integrity, and efficiency. Five Key Things I Have

Halfway through this course, I now better understand significantly both the theory and the practice of database systems. Here are five important takeaways of the first portion of the class: 1. The Relational Model and Its Relevance I learned how the relational model forms the basis of contemporary data systems, structuring data into tables with

Example of a Non-Key JoinWhile most SQL joins are performed using primary key–foreign key relationships, there are situations where a join is based on a non-key condition. For instance, consider the following scenario: we want to identify employees whose hourly wage exceeds the budget-per-hour allocated to certain projects. This allows management to quickly identify assignments

Example of a Non-Key Join:  In most practical scenarios, SQL joins aren’t limited to primary key–foreign key joins. Instead, data might be joined by comparisons, ranges, or some other business rule as determined by analysts or developers. For instance, let’s say we’re interested in finding employees whose hourly pay is higher than the spend-per-hour available

Orientation and readings this week gave me a good grounding in the necessity of relational databases within data management. At first glance, relational database tables are similar in many ways to spreadsheets—they’re rows and columns and are utilized in organizing data. However, one significant difference that I was taught is that relational databases are more

Looking back on HW1 from early in the semester, it is clear to me how much progress I have made as a programmer. At that time, I would approach problems with a more try-it-and-see method, often resorting to guessing over planning. Now, I to revisit HW1 today and I would first break down the problem

I spent this week on the Markov assignment and teamed up with my fellow student Taylor, also receiving 19.5 out of 20 for the project. Both of us treated the assignment consecensively and not only considered making the code work but also how to make the code more beautiful and user-friendly. Teamwork helped us to