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

Database AI Agents: The Read-Only Rule

By

Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A...

Creating a SQL Stored Procedure to Load a SCD2

By

This is a blog that I am writing for future me and hopefully it’ll...

Funny Money: #SQLNewBlogger

By

While wandering around the documentation looking for some Question of the Day topics, I...

Read the latest Blogs

Forums

Pro SQL Server Internals

By Site Owners

Comments posted to this topic are about the item Pro SQL Server Internals

SQL ART: Who's Blocking Who? Visualising SQL Server Blocking With Spatial Geometry

By Terry Jago

Comments posted to this topic are about the item SQL ART: Who's Blocking Who?...

Running SQLCMD II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Running SQLCMD II

Visit the forum

Question of the Day

Running SQLCMD II

I run this command to start SQLCMD:

sqlcmd -S localhost -E -c "proceed"
At the prompt, I type this (the 1> and 2> are prompts):
1> select @@version
2> go
What happens?

See possible answers