Articles

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.

2015-11-23

3,694 reads

Blogs

Flyway Tips: AI Helps with Commit Messages

By

At Redgate, we’re experimenting with how AI can help developers and DBAs become better...

Startup scripts in SQL Server containers

By

I was messing around performing investigative work on a pod running SQL Server 2025...

Using SQL Compare with Redgate Data Modeler

By

Redgate recently released SQL Compare v16, which included a new feature to work with...

Read the latest Blogs

Forums

What is Page Density

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What is Page Density

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

By Steve Jones - SSC Editor

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

Azure-SSIS, Self-Hosted Integration Runtime, & Data Gateway?

By jasona.work

Looking to confirm my understanding of these three products and how they can be...

Visit the forum

Question of the Day

What is Page Density

In SQL Server, there is a concept of page density. This is determined by how much data is stored on each page. What is a page density of 90%?

See possible answers