Articles

External Article

Finding a better candidate for your clustered indexes

When creating tables it is difficult to determine exactly how the data will be accessed. Therefore when clustered indexes are chosen they are often just the ID column that makes the row unique. This may be a good choice, but once the application has been used and data access statistics are available you may need to go back and make some adjustments to your tables to ensure your clustered indexes are providing a benefit and not a drain on your applications.

2008-12-26

3,880 reads

Blogs

Advice I Like: Ranch Rules

By

Leave a gate behind you the way you first found it. – from Excellent...

Fix Slow, Bloated MSDB: Purge Old History And Add Missing Indexes

By

Fix Slow, Bloated MSDB: Purge Old History And Add Missing Indexes ...

Three Ways to Use Snowflake Data in Microsoft Fabric

By

Organizations increasingly want Snowflake and Microsoft Fabric to coexist without duplicating data or fragmenting...

Read the latest Blogs

Forums

25 Years of SQL Server Central

By Steve Jones - SSC Editor

Comments posted to this topic are about the item 25 Years of SQL Server...

The Decoded Value

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Decoded Value

Deploying SQL Server Developer Edition in Kubernetes: A Cost-Effective Alternative to RDS

By Sujai Krishna

Comments posted to this topic are about the item Deploying SQL Server Developer Edition...

Visit the forum

Question of the Day

The Decoded Value

In SQL Server 2025, what is returned from this code: 

DECLARE @message VARCHAR(50) = 'Hello SQL Server 2025!';
DECLARE @encoded VARCHAR(MAX);

SET @encoded = BASE64_ENCODE(CAST(@message AS VARBINARY(1000)));
SELECT BASE64_DECODE(@encoded)

See possible answers