2005-09-19
2,089 reads
Performance Tuning
Controlling Transactions and Locks in SQL 2000 and 2005 - Part 2
In order for a transaction to meet the requirements of ACID, locks are employed to insure data integrity and multi-user access. The scope, or number of rows held by a lock, is referred to as Lock Granularity. This month, we will begin by introducing several different types of lock modes employed by MS SQL.
2005-09-16
3,544 reads
Finding Duplicate Indexes in Large SQL Server Databases
One important component of tuning a large, heavily used database, is to ensure that the tables are indexed optimally: enough indexing, but not too much indexing for the application you are running. There are rules of thumb about index tuning, but the entire issue is so complex that there's no "silver bullet" solution that will work for every case. However, in tuning indexes we can generally say that it's not a good idea to maintain duplicate indexes on the same data. SQL Server does not provide checks to prevent duplicate indexes from being created, as long as the names are different
2005-09-05
3,192 reads
Are UDFs Harmful to SQL Server Performance?
SQL Server 2000 introduced user-defined functions (UDFs), and they were immediately hailed as a great tool for encapsulating repetitive code, as well as allowing you to perform more complicated processing directly in an SQL expression. On its face, that claim is valid. You can certainly improve readability and maintainability with UDFs. But cleaner code will be cold comfort if your queries bog down and lock up your server.
2005-08-31
3,336 reads
Performance Monitoring by Internal Fragmentation Measurement
It has not been clear to what extent fragmentation, either internal or external, truly affects the performance of your SQL Server 2000 databases. New author Koby Biller discusses some of the impacts that it could have and has a free tool for download that can help you determine how fragmented your disk truly is.
2005-08-16
9,704 reads
Controlling Transactions and Locks in SQL 2000 and 2005 - Part 1
A look at controlling transactions and locks with hints and snapshots in SQL Server 2000 and 2005.
2005-08-12
3,224 reads
2005-08-03
2,037 reads
2005-08-02
2,091 reads
2005-07-29
1,786 reads
Optimize SQL Server hardware performance
Tuning SQL Server for performance is in many ways like constructing a house. You must find a suitable location with rich soil, build a solid foundation to support two or three levels, install the electrical and plumbing, finish the walls for painting and decorating, and finally conduct ongoing maintenance.
2005-07-19
4,034 reads
Blogs
Running a Local LLM On Your Laptop Resources
By Steve Jones
Thanks to everyone that attended my sessions at VS Live San Diego yesterday. It...
Differences Between xp_readerrolog and sp_readerrorlog: #SQLNewBlogger
By Steve Jones
I was creating a question on sp_readerrorlog and realized that this procedure is different...
Why sys.fn_dblog Is Undocumented And Why It's Still There
By SQLPals
Why sys.fn_dblog Is Undocumented And Why It's Still There Why sys.fn_dblog...
Forums
Implementing Type 4 Slowly Changing Dimensions in SQL Server
Comments posted to this topic are about the item Implementing Type 4 Slowly Changing...
The Disabled Index
Comments posted to this topic are about the item The Disabled Index
Server-Level Table sizes
Comments posted to this topic are about the item Server-Level Table sizes
Question of the Day
The Disabled Index
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