Articles

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.

2012-11-23 (first published: )

7,126 reads

Blogs

Visualising Vectors in High Dimensional Space

By

Following on from my previous post on building The Burrito Bot, I want to...

The Intersection Between DevOps and FinOps

By

DevOps is about shortening the system development lifecycle. Plan faster, build faster, test faster,...

Fabric Mirroring doesn’t start copying Rows

By

A short blog post about an issue with Fabric Mirroring (with Azure SQL DB...

Read the latest Blogs

Forums

PostgreSQL String Functions Part 1

By Shivayan Mukherjee

Comments posted to this topic are about the item PostgreSQL String Functions Part 1

Working Better Under Pressure

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Working Better Under Pressure

Identities and Sequences V

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identities and Sequences V

Visit the forum

Question of the Day

Identities and Sequences V

When thinking about the identity property and sequence objects, which of these can generate values before an insert statement is executed?

See possible answers