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.

Blogs

Advice I Like: Lots of Ideas

By

“A multitude of bad ideas is necessary for one good idea” – from Excellent...

Microsoft Fabric Data Agents: Bringing Structured and Unstructured Data Together

By

Most enterprise questions do not live neatly in one place. The numbers may be...

Keeping Redshift System Table History Past 7 Days with S3 Tables

By

Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...

Read the latest Blogs

Forums

Parameter Sensitive Plan Optimization vs. Parameter Sniffing: What SQL Server Fixes and What It Doesn't

By vgupta

Comments posted to this topic are about the item Parameter Sensitive Plan Optimization vs....

Hyperscale Replicas I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Hyperscale Replicas I

The End of Summer

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The End of Summer

Visit the forum

Question of the Day

Hyperscale Replicas I

What types of secondary replicas are available for the Azure SQL Database Hyperscale edition?

See possible answers