Troubleshooting Slow Queries That Already Have an Index
This article looks at some common query patterns that cause performance issues and provides some guidance on how to fix them.
2026-11-02
2,740 reads
This article looks at some common query patterns that cause performance issues and provides some guidance on how to fix them.
2026-11-02
2,740 reads
Many systems expect a sequential range of numbers for invoices, ticket numbers, and more. Learn how you can identify where you have gaps in your sequences.
2026-09-21
3,909 reads
In Part 2 of this series we learn how OUTER APPLY can be used in your queries to return data, even when there are no matches between tables.
2026-08-12
3,509 reads
As database changesets accumulate over time, they gradually become more than deployment artifacts. This level explores how a well-organized changeset library evolves into a replayable representation of the database’s structural history, supporting not only reliable deployments but also reconstruction, auditing, and long-term maintainability. Through practical examples and a real-world case study, it shows why maintaining coherent Create and Rollback scripts continues to provide value long after a successful production deployment.
2026-08-05
717 reads
Learn the basics of the CROSS APPLY operator with a few examples in this short piece.
2026-07-27
6,621 reads
This article shows how the TRY_PARSE() and TRY_CONVERT() functions can be used to handle data quality issues and ensure that your software continues to function without throwing errors.
2026-07-13
3,870 reads
Learn about an alternative strategy for avoiding hardcoded literal values in SQL Server queries by using single-row views designed to mimic enum behavior.
2026-06-26
3,604 reads
As database development scales across multiple contributors, concurrency becomes an inherent aspect of the process. Changes that are individually correct may still conflict when developed against a shifting baseline. This level introduces a disciplined approach to managing parallel changesets by controlling their scope, identifying overlap, and resolving conflicts through realignment. By ensuring that only one changeset retains its original baseline while others are adapted accordingly, deployments remain predictable and consistent. Once released, changesets are treated as immutable, and further evolution proceeds through new, forward-only changes.
2026-06-24
1,250 reads
This level examines how a rehearsed changeset is transformed into production-ready deployment artifacts. By consolidating scripts into controlled execution units and validating the resulting artifacts, the approach ensures that production deployment remains predictable and aligned with what was proven during rehearsal.
2026-06-10
1,221 reads
Introduction When developers first learn SQL aggregation, they usually start with the GROUP BY clause. It works well for summary reports because it combines multiple rows into a single result for each group. For example, you can calculate total sales per region or average salary per department. The limitation of GROUP BY appears when you […]
2026-06-05
4,718 reads
By Rayis Imayev
"I've seen things you people wouldn't believe..."— Roy Batty, Nexus-6 Replicant, Blade Runner (1982)(2026-Nov-08) Yep,...
By Steve Jones
We’ve celebrated our birthday many times at Redgate. In the Book of Redgate –...
Discover how Palantir connects enterprise data, supports AI-driven decision-making and helps companies turn insights...
Comments posted to this topic are about the item Pay for Performance, which is...
WhatsApp:0817819444 Jl. Mangunsarkoro No.24, Pamoyanan, Kec. Cianjur, Kabupaten Cianjur, Jawa Barat 43211
WhatsApp:0817819444 Jl. HOS Cokro Aminoto No.56-58, Muka, Kec. Cianjur, Kabupaten Cianjur, Jawa Barat 43215
I have a table, dbo.MasterBrands, with this data:
BrandID OfficialName 1 Samsung 2 Apple 3 Microsoft 4 Adidas 5 Coca-ColaI run this query. What is returned for Coca-Cola?
SELECT CHOOSE(BrandID, 'Conglomerate', 'Tech and Design', 'Desktop', 'Apparel') FROM dbo.MasterBrands;See possible answers