Competitions /Contest workspace
Contest mode● Checking judge…
TEAM SQL COMPETITION

Your SQL workspace.

Solve the selected problems. Earn your place on the leaderboard.

TIME ALLOWED90:00
Loading competition environment…
SQL 01_active.sql✓ Draft saved locally
commerce SQL practice
Ctrl + Enter to runLn 1, Col 1
Ready when you are
No query executedRead-only · 5s query limit
Drafts autosave on this deviceCorrectness first. Every accepted answer keeps its points.
READY TO PUT SQL TO WORK?

Your challenge starts here.

Start a 90-minute team practice session.
TEAM STANDINGS

The leaderboard

Ranked by score, then time the score was first achieved. Exact ties share a rank.

Fair play. Clear rules.

  1. One team, one PC, 90 minutes. The moderator selects the active problems. Points are shown beside each problem.
  2. Run, then submit. Sample runs do not affect your score. Server submissions must pass every test to earn points.
  3. Results matter. Return exactly the named columns in order. Required row ordering and duplicates are checked. Numeric tolerance: 0.000001.
  4. Three attempts per problem. Each failed server submission deducts 2 points, including SQL errors and time limits. Solved problems close to further submissions. Sample runs and infrastructure errors use no attempts. Wait five seconds between submissions.
  5. Ranking. Net score = earned points minus failed-attempt penalties, with a minimum of zero. Only active problems count. Highest score ranks first; ties use the shortest total solve time (sum of elapsed time from team start to each first accepted submission). Exact ties share a rank.
  6. Read-only SQL. SELECT and non-recursive CTEs only. Five seconds per query, 1,000 output rows maximum.
  7. Work with your teammates. Supplied schema and MySQL documentation are allowed. Use one PC per team. No AI, outside help, or sharing solutions between teams in an official contest.
  8. Interruptions. The server controls official time. Drafts save locally. Infrastructure errors earn no penalty; ask the organizer for a documented extension.

Browser practice uses inspectable sample data and SQLite. Official use requires the configured MySQL judge and organizer-issued team codes.