Many application performance problems can be traced to poorly performing database queries; however, there are many ways you can improve database performance. SQL ServerTM 2005 gathers a lot of information that you can use to identify the causes of such performance issues.
2008-01-11
3,144 reads
2008-02-21 (first published: 2008-01-09)
2,010 reads
Every developer needs to ensure that each TSQL statement is optimized. This article will give you a few different ideas on how to identify slow running queries and provide you with some tips on monitor your query performance while you make iterative changes to each query to try and improve performance.
2008-01-08
4,445 reads
Locking is a major part of every RDBMS and is important to know about. It is a database functionality which without a multi-user environment could not work. The main problem of locking is that in an essence it's a logical and not physical problem. This means that no amount of hardware will help you in the end. Yes you might cut execution times but this is only a virtual fix.
2008-01-03
4,767 reads
Now that you know how to speed up your SQL Server database queries, you can start delving into some of the more advanced tuning options.
2007-12-20
4,971 reads
If you've worked with SQL Server databases for any amount of time, it's practically a given that you've run into slow running queries. Learn how you may be able to improve performance by knowing what to look for in your query designs.
2007-12-17
7,707 reads
Find out how to update and tune table statistics in SQL Server to ensure data accuracy and boost performance. Learn auto and manual update commands.
2007-11-09
4,503 reads
Find pointers to optimize tempdb performance in SQL Server by striping and splitting across multiple files in SQL Server 2005.
2007-11-07
3,737 reads
When it comes to performance tuning, locating the problem index is one of the first steps and being able to very quickly narrow the focus of your efforts makes for a much more efficient DBA.
2009-03-27 (first published: 2007-11-06)
26,249 reads
Will changing to bulk recovery mode before running DBCC REINDEX help you avoid large log files? András investigates
2007-10-02
2,168 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