New author Nilav Ghosh brings us a performance tuning article to help your queries run better. This article examines how indexes can help reduce blocking.
2013-11-15 (first published: 2009-07-07)
22,368 reads
This article describes a utility that allows you to inspect cached plans and extract information that can be useful in improving the performance of your SQL.
2012-06-22 (first published: 2009-06-11)
47,575 reads
This article describes different ways of improving the performance of SQL Server queries, with a focus on index optimization.
2009-05-08
5,250 reads
In the first part of this series of articles, Gail showed how to find the procedures that contributed most to performance problems. In this final part, she shows how to use query statistics to pinpoint the queries that are causing the biggest problems, and then use the query execution plans to find out which operations are the root cause.
2009-05-04
4,867 reads
I was a running a routine query using an equal operator on the only column of the primary key for a table and I noticed that the performance was terrible. These queries should have been flying because all I was doing was retrieving one row of data which should have been doing an index seek. When I looked at the query plan it was doing a scan instead. This tip shows you what I found and how to resolve the problem.
2009-04-27
3,197 reads
To tackle performance problems with applications, first use SQL Profiler to find the queries that constitute a typical workload: From the trace, spot the queries or stored procedures that are having the most impact. Then it's down to examining the execution plans and query statistics. You then see what effects you've had and maybe repeat the process. Gail explains all, in a two-part article.
2009-03-23
5,352 reads
2008-12-23
3,802 reads
I can run the Database Tuning Advisor or examine the query plans, but is there any easier way to determine which indexes may be needed?
2008-12-08
2,297 reads
2008-11-19
3,163 reads
We are required to report from our SQL Server 2005 database. There are five or six tables regularly used for holding the reporting data, but these tables have five-to-seven million rows of data in them already. We need to use these tables consistently and our performance involving reporting is struggling. Do you have any tips to help improve it?
2008-10-22
4,961 reads
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...
When I put together the invitation for T-SQL Tuesday #202, I wasn't sure what...
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