Database Systems: Formula Sheet

Database Systems: Formula Sheet

Build a responsible reference sheet of relationships, conditions, units, representations, and decision rules rather than copying unexplained formulas. Develops data modeling, relational design, SQL, transactions, indexing, and responsible data management. Course titles, local sequences, grading, safety rules, required tools, and assessment formats vary; align this resource with the current syllabus and instructor directions.

Learning outcomes

• Explain and apply entity relationships, then connect it to relational normalization using course-appropriate evidence.
• Explain and apply relational normalization, then connect it to SQL queries using course-appropriate evidence.
• Explain and apply SQL queries, then connect it to transactions using course-appropriate evidence.
• Explain and apply transactions, then connect it to indexes and query plans using course-appropriate evidence.
• Explain and apply indexes and query plans, then connect it to entity relationships using course-appropriate evidence.

Prerequisite readiness

programming or structured logic, sets, basic data literacy, and precise specification Use a short ungraded check, repair the smallest missing skill, and immediately retest it in a course-level task.

Reference-sheet entries

• entity relationships: record its governing relationship or decision rule, required conditions, units or evidence, one representation, and a common misuse.
• relational normalization: record its governing relationship or decision rule, required conditions, units or evidence, one representation, and a common misuse.
• SQL queries: record its governing relationship or decision rule, required conditions, units or evidence, one representation, and a common misuse.
• transactions: record its governing relationship or decision rule, required conditions, units or evidence, one representation, and a common misuse.
• indexes and query plans: record its governing relationship or decision rule, required conditions, units or evidence, one representation, and a common misuse.

Use test

Can you choose the right relationship on an unlabeled task and explain why its conditions hold? If not, the sheet is storage rather than understanding.

Reliable method

identify entities and rules, design keys and constraints, normalize, query, test integrity, and inspect performance Keep assumptions, intermediate reasoning, units, sources, tool use, and checks visible so another learner can follow the decision process.

Representative application

Design a registration database that prevents impossible enrollments while supporting schedule and prerequisite queries. Predict a reasonable result before working, compare the outcome with the prediction, and explain limitations or alternative interpretations.

Error recovery

Watch for using a table as a spreadsheet without keys, constraints, normalization, transaction boundaries, or privacy rules. Mark the first unsupported move, classify the cause, correct the reasoning, and schedule a fresh mixed recheck after a delay.

Accessibility, integrity, and safety

Use approved accommodations and accessible formats. Follow course rules for collaboration, citation, calculators, software, generative tools, laboratories, clinical settings, field activity, privacy, copyright, and human or animal subjects. Never use Exams.fit to obtain protected questions or bypass assessment rules.

Evidence to save

When permitted, preserve a schema, sample data, validated queries, integrity tests, and design rationale with the prompt, first attempt, feedback, revision, verification, and reflection. Remove restricted assessment content and private or proprietary information.

Open-learning reference

Compare this original Exams.fit resource with the relevant OpenStax collection and MIT OpenCourseWare when they match the local course. Reviewed August 2, 2026. This page does not replace the current syllabus, instructor, institution, or qualified professional.