I Just Don’t Understand Why You Don’t Update SSMS.
A long time ago in a galaxy far, far away, SQL Server Management Studio was included as part of the SQL Server installer.
2026-02-20
Additional Articles
Azure Functions: The Serverless Powerhouse
Today’s organization are faced with multiple conflicts for their current cloud infrastructures and which approach to go with either opting for a microservice or monolith applications. However, there are numerous difficulties with standard hosting methods.
2026-02-18
Securing Your Databases in 2026: Best Practices for the Evolving Threat Landscape
In 2026, your approach to both applications and databases must be focused on practical and technical real-world operations and use cases rather than just hype.
2026-02-16
Exploiting SQL Server Date Correlation Optimization: How Tampered Backups Enable Cross-Database Data Leaks
This article reveals a critical SQL Server flaw: attackers can weaponize Date Correlation Optimization (DCO) views in restored backups
2026-02-13
Using REGEXP_COUNT to Count Strings in SQL Server 2025
We need to find out how many times certain strings appear in a column. We’ve used the LEN and REPLACE functions for years, but recently heard about REGEXP_COUNT and want to evaluate it, since we plan to upgrade to SQL Server 2025. How can we test this new feature?
2026-02-11
Common Misconceptions About Microsoft Certification Exams
An experienced exam writer explains common misconceptions about Microsoft certification exams, question design, preparation, and real-world expectations.
2026-02-09
How Filters and Sorting can Derail SQL Pagination Performance
In my previous tip, Pagination Performance in SQL Server, I showed how to make SQL pagination more predictable – turning O(n) into O(1). I materialized and cached row numbers to page through instead of calculating them on every request. It wasn’t the whole story, though; real pagination queries rarely get to sort without filtering. Users always want more control, and filtering can threaten that predictability.
2026-02-06
Common SQL Server Problems: Invalid Length
This is another part in my series designed to offer guidance around common issues in SQL Server. Today, let’s talk about the all-too-common error: invalid length.
2026-02-04
Database Development with AI in 2026
This seems like the appropriate first BrentOzar.com blog post in the year 2026, eh?
2026-02-02
Exploiting SQL Server Date Correlation Optimization: How Tampered Backups Enable Cross-Database Data Leaks
This article is a follow-up to SQL Server DBaaS Vulnerability: Decrypting System Code & Exfiltrating User Data, in which we saw some vulnerabilities that affected pretty much all DBaaS offerings available in the cloud. Now, we’ll look at another vulnerability that once again affects every major cloud vendor.
2026-01-30
Blogs
A bespoke reporting solution doesn’t have to cost the earth
By ChrisJenkins
You could be tolerating limited reporting because there isn’t an off the shelf solution...
Presenting with Visual Studio Code
A while back I wrote a quick post on setting up key mappings in...
Advice I Like: In 100 Years
By Steve Jones
In 100 years a lot of what we take to be true now will...
Forums
AllocationType as ROW_OVERFLOW_DATA
Hello, I inherited a number of tables with like 20-30 column using nvarchar(256) in...
is it true we cant debug c# scripts in ssis anymore under vs
Hi, i'm running vs2022. I'm trying out a c# script that i'd like to...
Question of the Day
Missing the Jaro Winkler Distance
I upgraded a SQL Server 2019 instance to SQL Server 2025. I wanted to test the fuzzy string search functions. I run this code:
SELECT JARO_WINKLER_DISTANCE('tim', 'tom')
I get this error message:Msg 195, Level 15, State 10, Line 1 'JARO_WINKLER_DISTANCE' is not a recognized built-in function name.What is wrong? See possible answers