External Article

Determine SQL Server memory use by database and object

For many people, the way that SQL Server uses memory can be a bit of an enigma. A large percentage of the memory your SQL Server instance utilizes is consumed by buffer pool (essentially, data). Without a lot of digging, it can be hard to tell which of your databases consume the most buffer pool memory, and even more so, which objects within those databases. This information can be quite useful, for example, if you are considering an application change to split your database across multiple servers, or trying to identify databases that are candidates for consolidation.

Blogs

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...

JSON_OBJECTAGG is an Aggregate: #SQLNewBlogger

By

I wrote an article recently on the JSON_OBJECTAGG function, but neglected to include an...

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