This article introduces some techniques that will allow you to pinpoint exactly where the performance issues are in your system, so you'll know exactly where to spend your time (and money) in solving them.
2007-04-03
2,360 reads
In SQL Server 2005, there is a new feature called Plan Guides that can help out in some cases where you discover poorly performing queries that you don't have direct control over. Essentially, a Plan Guide allows you to add or modify query hints to queries on the fly, just before they are executed.
2007-02-26
2,178 reads
2007-02-21
3,644 reads
Stored procedures can be an effective way to handle conflicting needs, but it's not always so obvious how to write them so they both perform well and scale.
2008-01-30 (first published: 2007-02-05)
10,708 reads
I recently read a blog post on doing case-insensitive text searches on SQL Server 2005. The post said that an index on a computed column might be used even if the computed column itself wasn't used in the WHERE clause. I was curious to test that and see how far I might take it.
2007-01-29
3,398 reads
Using hints in a query is something that most DBAs don't ever seem to bother with, but when they do, NOLOCK seems to be their hint of choice. Wayne Fillis brings us a detailed examination of how this particular hint actually affects the performance of your system.
2007-12-17 (first published: 2007-01-24)
72,641 reads
How should you approach indexing your database? Do you have a good strategy for deciding which indicies to create and on which columns? Aaron Ingold brings us a great article discussing these very topics that is likely to become a must read for many DBAs.
2007-12-24 (first published: 2007-01-08)
21,752 reads
SQL Server guru David Poole takes a look at the different integer data types and the impact of each of those on your database.
2007-12-10 (first published: 2006-12-18)
23,501 reads
The benefits of SQL Server 2005's new snapshot isolation feature are well known, but SQL Server developers also need to understand the downstream ramifications of snapshot isolation.
2006-12-11
2,303 reads
Most SQL Server programmers know to use the SET NOCOUNT command to prevent the number of rows message from being returned to the client. But how does this affect performance? Does it make sense to qualify the owner on your objects? SQL Server guru David Poole brings us some performance analysis of how your stored procedures perform.
2007-12-07 (first published: 2006-12-11)
25,880 reads
By Steve Jones
Thanks to everyone that attended my sessions at VS Live San Diego yesterday. It...
By Steve Jones
I was creating a question on sp_readerrorlog and realized that this procedure is different...
By SQLPals
Why sys.fn_dblog Is Undocumented And Why It's Still There Why sys.fn_dblog...
Comments posted to this topic are about the item Implementing Type 4 Slowly Changing...
Comments posted to this topic are about the item The Disabled Index
Comments posted to this topic are about the item Server-Level Table sizes
I run this code on SQL Server 2022.
CREATE TABLE Drink
(
drinkid INT NOT NULL
CONSTRAINT DrinkPK PRIMARY KEY CLUSTERED,
drinkname VARCHAR(20),
rating NUMERIC(2, 1)
)
GO
INSERT INTO Drink
(
drinkid,
drinkname,
rating
)
VALUES
(1, 'Margarita', 4.5),
(2, 'Mojito', 4.3),
(3, 'Old Fashioned', 4.7),
(4, 'Martini', 4.4),
(5, 'Cosmopolitan', 4.2)
GO
ALTER INDEX drinkpk ON dbo.drink DISABLE
GO
SELECT * FROM dbo.Drink
GO
What is the result? See possible answers