Articles

Technical Article

No Significant Fragmentation? Look Closer…

If you are relying on using 'best-practice' percentage-based thresholds when you are creating an index maintenance plan for a SQL Server that checks the fragmentation in your pages, you may miss occasional 'edge' conditions on larger tables that will cause severe degradation in performance. It is worth being aware of patterns of data access in particular tables when judging the best threshold figure to use.

You rated this post out of 5. Change rating

2012-03-14

3,229 reads

Blogs

Runing tSQLt Tests with Claude

By

Running tSQLt unit tests is great from Visual Studio but my development workflow...

Getting Your Data GenAI-Ready: The Next Stage of Data Maturity

By

I remember a meeting where a client’s CEO leaned in and asked me, “So,...

Learn Better: Pause to Review More

By

If you want to learn better, pause more in your learning to intentionally review.

Read the latest Blogs

Forums

The Long Name

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Long Name

Eight Minutes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Eight Minutes

T-SQL in SQL Server 2025: Fuzzy String Search I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item T-SQL in SQL Server 2025:...

Visit the forum

Question of the Day

The Long Name

I run this code to create a table:Create table with unicode nameWhen I check the length, I get these results:Table with length of name shown as 132 charactersA table name is limited to 128 characters. How does this work?

See possible answers