Bijay Kumar Sahoo
A payroll dashboard skips second place after two employees share the highest salary. Another report forces those same employees into different positions. Both queries run without errors, but neither matches the business requirement: equal salaries should share a rank, with no gaps afterward. The DENSE_RANK SQL function solves that problem. It assigns consecutive ranks to … Read more
A payroll report lists the lowest-paid employee twice because two people earn the same amount. A developer skips the first row to find the second-lowest salary, but the query returns that same minimum again. The statement runs successfully; the business answer is wrong. Understanding how to find the second lowest salary in SQL Server starts … Read more
A payroll dashboard shows the lowest salary as zero, but HR says no active employee earns that amount. The query runs successfully. The problem is that it mixes placeholder values, inactive employees, and legitimate salaries without defining which records belong in the report. Knowing how to find the lowest salary in SQL Server starts with … Read more
A payroll report can return the wrong employee even when its SQL runs without errors. Two employees share the highest salary, and a query that simply selects the third row reports the second-highest salary instead of the third distinct amount. Understanding how to find 3rd highest salary in SQL Server starts with defining what “third … Read more
A payroll analyst at a mid-size staffing company once sent me a screenshot of a report. It showed the “third highest salary” in a department, and the number was wrong. Two people shared the top salary, and the query counted them as separate ranks. The report fed a compensation review, so a small logic bug … Read more
A payroll analyst at a mid-sized staffing company once sent me a spreadsheet and a worried email. Their HR dashboard showed the “second highest salary” per department, but two departments returned the same number as the top salary. The query had used TOP 1 with a sort, and it counted tied employees as separate ranks. … Read more
A retail client once called me because their order report had gone from 8 seconds to 14 minutes. Nothing had changed except one thing. A developer had wrapped a tax calculation in a user-defined function and called it for every row in a 3-million-row table. The query looked clean, but it ran one function call … Read more
A manufacturing client called me on a Friday afternoon. Their only database administrator had left the company two weeks earlier, and nobody knew the sa password. The ERP system still ran, but a vendor needed to patch it that night. Every attempt to sign in with the old credentials ended in the same login failure. The good … Read more
A retail company called me on a Monday morning because its order app had stopped working. The error message said “A network-related or instance-specific error occurred,” and the team had already restarted the app servers twice. Nobody had checked whether the app servers could even reach the database. It turned out someone had changed a … Read more
When I trained a new database developer on my team last year, one of the first questions he asked me was, “How do I actually save this stored procedure once I’ve written it?” It’s a fair question, because unlike saving a Word document or an Excel file, saving a stored procedure in SQL Server doesn’t … Read more