What is sql-sales-management-system?

This project is a SQL learning exercise built around a fictional sales business. It uses Microsoft SQL Server to manage customers, products, suppliers, employees, orders, and the details of each order. The goal is to show how a set of SQL concepts work together on a realistic business dataset, rather than teaching each concept in isolation. The database has eight linked tables covering categories, suppliers, customers, employees, shippers, products, orders, and order details, connected with primary and foreign keys. On top of that structure sit more than 50 SQL queries organized into numbered scripts, starting with basic selects and filtering, moving through joins, set operators like union and intersect, string and date functions, grouping and having clauses, and views. The final scripts apply all of this to business questions such as finding best selling products, identifying high value customers, and building revenue reports. To try it, you clone the repository, open it in SQL Server Management Studio, and run the numbered SQL scripts in order, starting with creating the database and tables, then inserting sample data, then working through each topic script. The README includes screenshots of query results for each stage so you can see what the output should look like before running anything yourself. This is aimed at people learning SQL, particularly those studying for interviews or coursework that covers joins, aggregate functions, and reporting queries against a database that resembles a real store. It is not a production application. There is no user interface, no backend server, and no way to interact with the data outside of SQL Server itself. The author lists possible future additions such as stored procedures, triggers, common table expressions, window functions, indexes, and transactions, none of which are implemented yet. The technologies involved are Microsoft SQL Server, SQL Server Management Studio, Visual Studio Code, and Git. The project carries a license file, though the specific terms are not described in the README itself.