External Article

SQL Server Heaps, and Their Fragmentation

In SQL Server, heaps are rightly treated with suspicion. Although there are rare cases where they perform well, they are likely to be the cause of poor performance. If a table is likely to have a large number of changes, then it can become fragmented due to way that space is allocated and forward pointers used. How does one detect this problem? Is it significant? How does one deal with it, if necessary? Neeraj Tripathi explains.

Blogs

Google Moves Up Post-Quantum Cryptography Timeline

By

In cryptography, the RSA and ECC algorithms which we use primarily for asymmetric cryptography...

The Book of Redgate: No Politics

By

In today’s world, this might mean something different, but in 2010, we had this...

The Burrito Bot: AI-Powered Search in SQL Server 2025

By

A while back I posted about a couple of side projects that I’ve been...

Read the latest Blogs

Forums

Identities and Sequences II

By Steve Jones - SSC Editor

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

Using PostgreSQL as a NoSQL Store and a Search Engine

By sabyda

Comments posted to this topic are about the item Using PostgreSQL as a NoSQL...

Is Your Time "Free"?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Is Your Time "Free"?

Visit the forum

Question of the Day

Identities and Sequences II

In thinking about the differences between the identity property and a sequence object, which of these two guarantees that there are consecutive numbers (according to the increment) inserted in a single table?

See possible answers