External Article

SQL Server Transaction Log Fragmentation: a Primer

Generally, you will have no need to worry about the number of virtual log files in your transaction log. However, if you use the default settings for 'auto-grow', you can end up with such 'fragmentation' in your transaction log as to affect performance noticably. How can this be avoided? How can you tell it's a problem? What do you do about it? Greg explains.

Blogs

Ramblings about data communities and your contributions, no excuses

By

I have been active in the data community throughout my career. I have met...

SQL Server Journey till 2025 (brief)

By

Quick Summary for Microsoft SQL Server till 2025, I am fortunate to be part...

Building Power BI Reports: Desktop vs Fabric

By

Why this comparison feels confusing If you’re a Power BI report author who’s just...

Read the latest Blogs

Forums

Having a Little Fun at SQL Server Central

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Having a Little Fun at...

Designing SQL Server Pipelines That Are Ready for AI Before You Actually Need AI

By AR

Comments posted to this topic are about the item Designing SQL Server Pipelines That...

String Similarity I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item String Similarity I

Visit the forum

Question of the Day

String Similarity I

On SQL Server 2025, when I run this, what is returned?

SELECT EDIT_DISTANCE_SIMILARITY('SQL Server', 'MySQL')

See possible answers