This post is rather short, because it’s more of a link round-up than anything.
Read the post: Software Vendor Mistakes With SQL Server: Not Taking Advantage Of Index Compression
AI Training for Database Teams and SQL Server Performance Tuning
This post is rather short, because it’s more of a link round-up than anything.
Read the post: Software Vendor Mistakes With SQL Server: Not Taking Advantage Of Index Compression
It’s hard to believe that this is still a lively debate, given how far technology has come since the original conversations around if and when…
Read the post: Software Vendor Mistakes With SQL Server: Thinking Index Rebuilds Solve Every Problem
I can’t remember the last time I saw someone lower fill factor for a good reason. Perhaps those just aren’t the type of folks who need my help, or perhaps…
Read the post: Software Vendor Mistakes With SQL Server: Lowering Fill Factor For Every Index
In yesterday’s post, we covered some of the basics of designing nonslustered indexes to make queries go faster, but sometimes those aren’t quite enough.
Read the post: Software Vendor Mistakes With SQL Server: Not Using Filtered Indexes Or Indexed Views
There’s a bit of magic to index tuning, once you move beyond the basics. But we do have to start with the basics.
Read the post: Software Vendor Mistakes With SQL Server: Designing Nonclustered Indexes Poorly
Heaps aren’t always bad, but you have to be careful when you choose to use them, because the problems that sneak up with them are tricky to detect and…
Read the post: Software Vendor Mistakes With SQL Server: Avoiding Clustered Indexes
Like many things, applications tend to evolve over time. New and improved functionality, Bug Fixed And Performance Improvements™, and ever expanding schema…
Read the post: Software Vendor Mistakes With SQL Server: Not Indexing For Evolving Queries
Building on yesterday’s post about cleaning up old indexes: Once you’ve gotten rid of indexes that aren’t used anymore, you’re gonna have some more work to…
Read the post: Software Vendor Mistakes With SQL Server: Not Deduplicating Overlapping Indexes
The longer your application has been around, the more developers and queries it has seen. There are a lot of ways the indexes could look, depending on how…
Read the post: Software Vendor Mistakes With SQL Server: Not Cleaning Up Old Indexes
If your developers could intuit every possible way that your application could be used, and were really good at performance turning SQL Server, you…
Read the post: Software Vendor Mistakes With SQL Server: Not Letting Customers Add Indexes
Triggers can be quite useful to perform functions that cascading foreign keys are too simple for, but you can very easily overload them.
Read the post: Software Vendor Mistakes With SQL Server: Overly Complicated Triggers
I’ve had far too many clients get stuck running out of identity values for a table that grew a lot faster than they thought it would.
In an earlier post, we talked about how strings change the way SQL Server’s optimizer gives memory to queries under certain conditions.
Read the post: Software Vendor Mistakes With SQL Server: Using MAX Datatypes Unnecessarily
In yesterday’s post, I taught you about the good things that come from using computed columns.
One of the most common things I see when working with vendor apps are queries that need to filter or join on some expression that traditional indexing…
Read the post: Software Vendor Mistakes With SQL Server: Not Using Computed Columns
There’s a time and a place for everything, except scalar functions. In a lot of the locking and deadlocking issues I help clients with, developers either:
Read the post: Software Vendor Mistakes With SQL Server: Explicit And Implicit Transactions
I often see people get stuck hard by this. Even worse, it happens when they’re using a merge statement, which are like throwing SQL Server a knuckleball.
Read the post: Software Vendor Mistakes With SQL Server: Modifying Millions of Rows At A Time
For developers who have worked with, or who write applications that work across multiple database platforms, working with SQL Server can often be a jarring…
Read the post: Software Vendor Mistakes With SQL Server: Not Using An Optimistic Isolation Level
I totally understand the Cult Of NOLOCK. Blocking sucks. Fixing it is annoying. Read Committed is a garbage isolation level.
Read the post: Software Vendor Mistakes With SQL Server: Mistaking NOLOCK For Concurrency
It seems that most developers are either too naive or too lazy to choose just the columns that they need to satisfy a particular requirement, and so their…
Read the post: Software Vendor Mistakes With SQL Server: Selecting Everything From Everywhere
When it comes to weird performance problems, I’ve seen this cause all sorts of them. The worst part is that there are much smarter ways to handle this.
If you have a small to medium sized application, and your developers are highly skilled not only in their preferred method of development, and you have…
Continuing a bit on yesterday’s theme of parameterization, another type of mistake I see software vendors make quite a bit is not parameterizing queries at…
Read the post: Software Vendor Mistakes With SQL Server: Not Parameterizing Queries
Far and away, my most common clients are people who create or host applications that run on top of SQL Server.
Read the post: Software Vendor Mistakes With SQL Server: Not Strongly Typing Parameters
Copyright © 2019-2026 Darling Data