Articles

Technical Article

SQL in the City: Save the Date

SQL in the City is coming back to London and Seattle in 2014. The London event will take place on October 24 (before Tech Ed Europe) and in Seattle on November 3 (before PASS Summit). Keep an eye on the event website and @redgate for updates.

2014-07-21

11,275 reads

Technical Article

SQL Saturday #302 - Albany

SQL Saturday is coming to Albany, NY on July 26, 2014. This is a free full day of training and networking for SQL Server professionals. This event also features a paid-for precon session with Grant Fritchey on query performance tuning. The event is soon so register while space is available.

2014-07-16

9,085 reads

Technical Article

SQL Monitor Metric: Memory used by ad hoc queries running once

This metric measures the amount of memory used by the total number of ad hoc queries in the plan cache that have only run one time. This value is only accurate for the instant the query is run, and the value can change radically from one capture time to the next.

You rated this post out of 5. Change rating

2014-07-14

9,595 reads

Blogs

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

SWAG Saves the Day

By

PASS Summit East is in one week. I was on the road last week...

Read the latest Blogs

Forums

Increase Deadlock Detection

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Increase Deadlock Detection

A Tool is Better than a Script

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Tool is Better than...

Understanding Deadlock Victim Selection in SQL Server

By john.martin

Comments posted to this topic are about the item Understanding Deadlock Victim Selection in...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers