Module 1: Relational Database Foundations & SQL Server 2022 Workspace
You begin with how enterprises store operational truth: tables, schemas, primary keys, foreign keys, normalization intent, and why analysts must respect data integrity before writing flashy queries. We map business entities—customers, orders, products, payments—to relational structures and explain OLTP vs reporting-friendly design at a practitioner level. Then you configure the SQL Server 2022 practice environment, connect through SSMS and Azure Data Studio, understand instance vs database vs schema, and learn safe lab habits: SELECT-before-UPDATE discipline, transaction awareness, and backup/restore basics. May 2026 emphasis includes cloud-hybrid awareness (on-prem SQL Server feeding Azure SQL / Fabric-ready datasets) and the vocabulary Ahmedabad interviewers use when they ask about “writing production SQL,” not just classroom SELECT statements.
Module 2: T-SQL SELECT, Filtering, Sorting & Core Data Types
This module builds query fluency from the ground up using real business tables. You master SELECT lists, aliases, DISTINCT, WHERE filters with AND/OR/IN/BETWEEN/LIKE, NULL handling with IS NULL / COALESCE, ORDER BY, and TOP/OFFSET-FETCH paging patterns used in operational reports. Data type discipline covers numerics, decimals for money, dates/datetimes (and the 2022-era best practices to avoid implicit conversion bugs), Unicode text, and CAST/CONVERT for safe transformations. You practice readable formatting, commenting standards, and validating row counts before trusting aggregates—habits that separate analysts who break dashboards from those who earn trust. Lab scenarios include customer lists, overdue invoices, SKU filters, and branch-wise extracts mirroring MIS requests from trading and manufacturing firms in Gujarat.
Module 3: Joins, Subqueries, CTEs & Set-Based Thinking
Enterprise analytics lives in joined data. You implement INNER, LEFT, RIGHT, and FULL joins with clear ON predicates, avoid accidental Cartesian products, and use composite keys where business reality demands it. Subqueries (scalar, multi-row, correlated) are compared with JOIN rewrites so you choose readable, performant patterns. Common Table Expressions (CTEs) become your default tool for staged logic—cleansing steps, intermediate KPI tables, and recursive hierarchies (org trees, category rollups). UNION/EXCEPT/INTERSECT consolidate multi-source outputs where analysts merge legacy Excel uploads with SQL tables. By the end you can explain join cardinality to a hiring manager and debug “why did my row count double?”—a classic Ahmedabad practical-test failure point.
Module 4: Aggregation, GROUP BY, HAVING & Window Functions
Reporting KPIs require rigorous aggregation. You work through GROUP BY, HAVING, ROLLUP/CUBE/GROUPING SETS for subtotal reports, and conditional aggregates with CASE inside SUM/COUNT. Window functions unlock analyst-grade analytics without self-join hacks: ROW_NUMBER for deduplication, RANK/DENSE_RANK for leaderboard reports, running totals, moving averages, and LAG/LEAD for period-over-period comparisons. May 2026 drills reflect what BI teams actually request—daily sales vs target, cohort-style rep performance, inventory ageing buckets, and contribution margin by category. We also cover common pitfalls: grouping on non-aggregated columns, misusing DISTINCT with GROUP BY, and window frame boundaries that silently skew financial totals.
Module 5: Schema Design, Normalization, Constraints & Data Quality
Analysts who only query eventually hit walls when sources are poorly designed. You practice designing star-friendly schemas while respecting 3NF operational models: entities, relationships, surrogate keys, natural keys, and when denormalization is acceptable for reporting speed. Constraints include PRIMARY KEY, FOREIGN KEY, UNIQUE, CHECK, and DEFAULT rules that prevent dirty data at the door. You implement lookup tables, bridge tables for many-to-many relationships, and soft-delete patterns with effective dating where HR or CRM histories matter. Data quality exercises cover duplicate detection, orphan keys, referential integrity failures, and audit columns (CreatedOn, ModifiedBy). This module prepares you to collaborate with DBAs and senior developers instead of blaming “bad data” without evidence.
Module 6: Stored Procedures, Functions, Triggers & T-SQL Programmability
Production environments rarely expose ad-hoc query access; they expose controlled interfaces. You author stored procedures with parameters, set-based inserts/updates, TRY/CATCH error handling, and THROW for business rule violations. Scalar and table-valued functions are compared with procedures so you know performance trade-offs (especially with UDF pitfalls on large datasets). Triggers are introduced with caution—audit logging and derived maintenance use cases—along with why overusing triggers harms maintainability. Dynamic SQL is covered safely with parameterization to prevent injection risks when report filters must be flexible. Labs simulate MIS automation: month-end snapshot loads, parameterized branch dashboards, and reusable datasets for Power BI DirectQuery or Import models.
Module 7: Indexing, Execution Plans & Query Performance Tuning
Slow reports cost money. You read graphical and estimated execution plans, identify scans vs seeks, understand key lookups, spills, and cardinality estimation issues at an analyst-relevant depth. Index strategies include clustered vs nonclustered indexes, covering indexes, included columns, and when filtered indexes help selective reports. You learn to rewrite sargable predicates, avoid functions on indexed columns in WHERE clauses, and use appropriate statistics refresh awareness. Practical tuning labs take intentionally slow queries from FMCG-style sales history tables and improve them measurably—students document before/after duration and logical reads like a junior performance engineer. This is a high-value differentiator for Ahmedabad roles where teams say “we need someone strong in SQL,” not just Excel.
Module 8: Transactions, Security, Roles & Compliance-Aware Access
Data platforms must be trustworthy. You practice BEGIN/COMMIT/ROLLBACK transactions, understand isolation levels conceptually (READ COMMITTED vs repeatable read trade-offs), and see how deadlocks appear in concurrent posting scenarios. Security modules cover SQL logins vs Windows auth awareness, database users, roles, GRANT/REVOKE/DENY, schema ownership, and least-privilege access for analysts. Row-level security and dynamic data masking are introduced as modern 2022-era controls enterprises adopt for multi-branch reporting. You also learn export discipline—PII handling, masking phone/email in shared datasets, and why “SELECT * into Excel” can violate policy. These topics align with audit questions in IT services, BFSI, and corporate analytics teams hiring around Ahmedabad and Gandhinagar.
Module 9: Advanced Analytics SQL — PIVOT, JSON, Temporal Tables & Fabric-Ready Patterns
May 2026 analyst stacks expect more than basic SELECTs. You implement PIVOT/UNPIVOT and modern alternatives with conditional aggregation for cross-tab MIS layouts leadership still requests. JSON functions (OPENJSON, FOR JSON) connect SQL Server to API-fed pipelines and semi-structured exports common in integration projects. Temporal tables (system-versioned) support “as-of” reporting for price or policy changes. You build analyst views and semantic-friendly objects (views, indexed views where appropriate) that Power BI, Excel, and Python consumers can reuse without copying logic. Optional awareness covers linked servers, OPENROWSET patterns, and Azure SQL / Microsoft Fabric landing zones so you can discuss cloud analytics career paths credibly in interviews.
Module 10: Enterprise Capstone, Portfolio Delivery & Ahmedabad Hiring Drills
The capstone integrates everything into one employer-grade deliverable: design a normalized operational schema for an e-commerce and distribution business, load staged data with set-based T-SQL, build stored procedures for KPI datasets, apply window functions for retention and category contribution analysis, tune critical queries with indexes and plan review, and publish analyst-ready views for BI consumption. You submit a technical portfolio—ER diagram, core procedures, sample reports, and a performance note explaining one major optimization. Interview drills mirror 2026 hiring panels: explain a join vs subquery choice, walk through an execution plan, fix a non-sargable filter, describe transaction safety for month-end loads, and answer scenario questions for data analyst, MIS executive, SQL developer, and junior BI engineer roles across Ahmedabad, Gandhinagar, and nearby industrial corridors.