SQL Essentials with MariaDB is a hands-on course in SQL on MariaDB, from SELECT, joins and subqueries to CTEs, window functions and JSON, plus creating tables with constraints, indexes, views and transactions. It suits people starting a database career, developers and data analysts who work with MariaDB or MySQL and want practical, modern SQL skills.
SQL is still the most important basic skill for anyone who works with data, whether developer, data analyst or system administrator. MariaDB is a widely used open source database that runs websites, business systems and many systems migrated from MySQL. Yet many people can only write basic statements, and when a task calls for summarising several tables, ranking results or calculating running totals, they export the data to Excel and finish it there, even though modern SQL can do it in a single statement.
This course builds a solid SQL foundation on MariaDB 12.3 LTS, with hands-on practice in every topic. Learners install MariaDB with Docker and use database management tools, write SELECT queries with conditions, sorting, grouping, joins and subqueries, then move on to string, numeric and date functions, CTEs, window functions and JSON data. They go on to create databases and tables with constraints, use indexes and EXPLAIN, build views, manage data with INSERT, UPDATE and DELETE with RETURNING, and control transactions. The course ends with a workshop that answers business questions with SQL against a sample online store database. (3 days, 6 hours per day, 18 hours in total, Beginner to Intermediate level.)
Course Details
This course is the 2026 edition of SQL Essentials with MariaDB, updated for MariaDB 12.3, the latest LTS release. It runs for 3 days, 6 hours per day (18 hours in total, 09:00-16:00), as lectures with labs on a single sample online store database throughout. Beginner to Intermediate level. Day one covers SELECT, GROUP BY, joins and subqueries, day two covers functions, CTEs, window functions
and JSON, and day three covers creating tables, constraints, indexes, views, data changes and transactions. Every lab runs on the learner's own machine with Docker and free tools. The course focuses on writing SQL; learners who want to administer MariaDB, including backup and replication, can continue with the institute's MariaDB DBA course. Learners take home a docker-compose file, the sample database and the SQL files for every lab.
Section 1: Lab: Setting Up MariaDB 12.3 LTS and Tools
Section 2: Lab: Basic SELECT
Section 3: Lab: LIMIT, Aggregates and GROUP BY
Section 4: Lab: Joining Several Tables
Section 5: Lab: Subqueries
Section 6: Lab: Numeric and String Functions
Section 7: Lab: Dates, Times and Conditions
Section 8: Lab: CTEs and Recursive CTEs
Section 9: Lab: Window Functions
Section 10: Lab: JSON Data in MariaDB
Section 11: Lab: Creating Databases and Tables
Section 12: Lab: Constraints and Data Integrity
Section 13: Lab: Indexes, EXPLAIN and Views
Section 14: Lab: Managing Data and Transactions
Section 15: Workshop: Answering Business Questions with SQL
No public rounds are open right now. Join the waiting list and we will contact you first when the next round opens, or ask us on LINE. Or call 02-570-8449 or 088-807-9770
WHERE filters rows before grouping, so it works on individual row values but cannot use aggregate functions such as SUM or COUNT. HAVING filters after GROUP BY, so it can test each group's totals. For example, WHERE status = 'paid' keeps only paid orders, then GROUP BY customer_id with HAVING SUM(amount) > 10000 keeps only customers whose total exceeds the threshold.
GROUP BY collapses many rows into one per group, while a window function calculates across rows and keeps every row. That makes it ideal for ranking with ROW_NUMBER or RANK, comparing with the previous row using LAG, and running totals such as SUM(amount) OVER (PARTITION BY customer_id ORDER BY order_date). Note that you cannot use a window function in WHERE; calculate it in a subquery or CTE first, then filter the result.
A view is a saved query given a name so it can be used like a table, created with CREATE VIEW name AS SELECT. It stores no data itself: each time you query it, it reads the latest data from the underlying tables, whereas a table holds data on disk. Views hide complex queries and can limit users to certain columns or rows. Only simple views can be used to update data.
It suits people starting a database career, developers who use MariaDB or MySQL, data analysts who pull data themselves and administrators who want a solid SQL foundation. You should understand tables, rows and columns. No programming or previous MariaDB experience is needed, and you need a laptop that can run Docker Desktop.
You will be able to install MariaDB with Docker, write SELECT queries with conditions and grouping, use joins and subqueries, apply string, numeric and date functions, write CTEs and window functions, read JSON data, create and alter tables, constraints, indexes and views, and insert, update and delete data with RETURNING and transactions using COMMIT, ROLLBACK and SAVEPOINT. Participants who complete the training receive a Certificate of Completion with its own number, which can be verified online.
Yes. It can be run in-house for your team, with examples adapted to your own work, such as writing queries against table structures similar to the systems your team uses. You can request a quotation from this page, or contact us on LINE @itgenius or by phone on 02-570-8449.
Articles are published in Thai.
Deep learning is the engine behind the AI systems people use every day, from image classification and object detection on camera feeds to sentiment analysis of text and large language models. But the tools move fast: the TensorFlow 1 and Keras 2 style code…
Preparing data in Excel often takes longer than the analysis itself: copying sales files from several branches together, trimming spaces and fixing dates column by column, or turning a report exported from another system into a proper table, and then doing it…
Elasticsearch is a distributed search and analytics engine widely used both for search inside applications and for storing system logs so they can be investigated later, while Kibana is the interface for exploring that data and building charts and dashboards.…
