SQL Foundations Tutor Required
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted2 hours ago
CORE-103 Data & SQL Foundations. 10 topics.
Almost every system these students build or support will store its data in a
relational database, and almost every serious production incident involves one.
From what a database is for through querying, joins and aggregation to schema
design, transactions and indexing.
Real time goes to reconciliation - checking that a query returned the RIGHT
answer rather than a plausible one - because a wrong number delivered
confidently is worse than no number at all.
Note: this course shares ground with DB-101, the Databases track foundation, at
a much shallower depth. You will be asked to coordinate with that trainer so the
two reinforce rather than repeat each other.
THE 10 TOPICS — FIXED
1. What a database is for (6 h) - persistence, concurrency and integrity: the
three problems a file does not solve
2. Tables, rows and types (6 h) - schemas, primary keys, and column types
that make invalid data impossible to store
3. Querying with SELECT (6 h) - reading a question in English and writing it
in SQL
4. Joins and relationships (6 h) - one-to-many and many-to-many, and what
each join type does to rows that have no match
5. Aggregation and grouping (6 h) - with the grouping mistakes that quietly
produce a plausible wrong number
6. Writing data safely (6 h) - INSERT, UPDATE, DELETE and transactions
7. Normalisation, and when to stop (6 h) - and recognising when further
normalising costs more than it saves
8. Indexes and why queries are slow (6 h) - reading a query plan rather than
guessing
9. Checking a result is right (6 h) - reconciling a query against a known
total: the habit that catches a wrong report before a manager does
10. Designing a small schema (6 h) - turning a described business into tables,
keys and constraints, then defending the choices
BY THE END, A STUDENT CAN
- turn a described business situation into tables, keys and constraints, and
defend the choices
- answer a question posed in English with SQL, including across several related
tables
- check a result against a known total and find the error when the two disagree
- read a query plan and explain why a query is slow
- write data safely, understanding what a transaction protects them from
WHO WE WANT
Someone who has designed and queried real databases and who treats topic 9 -
checking a result is right - as the point of the course rather than a footnote.
Able to teach beginners. Able to write.
If you are also bidding on DB-101 (the Databases track foundation), say so; we
would rather one person held both than have them collide.
TO BID, ANSWER THESE
Almost every system these students build or support will store its data in a
relational database, and almost every serious production incident involves one.
From what a database is for through querying, joins and aggregation to schema
design, transactions and indexing.
Real time goes to reconciliation - checking that a query returned the RIGHT
answer rather than a plausible one - because a wrong number delivered
confidently is worse than no number at all.
Note: this course shares ground with DB-101, the Databases track foundation, at
a much shallower depth. You will be asked to coordinate with that trainer so the
two reinforce rather than repeat each other.
THE 10 TOPICS — FIXED
1. What a database is for (6 h) - persistence, concurrency and integrity: the
three problems a file does not solve
2. Tables, rows and types (6 h) - schemas, primary keys, and column types
that make invalid data impossible to store
3. Querying with SELECT (6 h) - reading a question in English and writing it
in SQL
4. Joins and relationships (6 h) - one-to-many and many-to-many, and what
each join type does to rows that have no match
5. Aggregation and grouping (6 h) - with the grouping mistakes that quietly
produce a plausible wrong number
6. Writing data safely (6 h) - INSERT, UPDATE, DELETE and transactions
7. Normalisation, and when to stop (6 h) - and recognising when further
normalising costs more than it saves
8. Indexes and why queries are slow (6 h) - reading a query plan rather than
guessing
9. Checking a result is right (6 h) - reconciling a query against a known
total: the habit that catches a wrong report before a manager does
10. Designing a small schema (6 h) - turning a described business into tables,
keys and constraints, then defending the choices
BY THE END, A STUDENT CAN
- turn a described business situation into tables, keys and constraints, and
defend the choices
- answer a question posed in English with SQL, including across several related
tables
- check a result against a known total and find the error when the two disagree
- read a query plan and explain why a query is slow
- write data safely, understanding what a transaction protects them from
WHO WE WANT
Someone who has designed and queried real databases and who treats topic 9 -
checking a result is right - as the point of the course rather than a footnote.
Able to teach beginners. Able to write.
If you are also bidding on DB-101 (the Databases track foundation), say so; we
would rather one person held both than have them collide.
TO BID, ANSWER THESE
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.