External Article

The SQL Server 2016 Query Store: Overview and Architecture

SQL Server's Query Store, introduced in SQL Server 2016, helps to troubleshoot query performance by capturing a range of information about query usage, CPU, memory consumption, I/O and execution time, and retaining every Execution Plan for analysis. Much of this information is available through queries. It looks set to be the most significant enhancement of SQL Server 2016 - Enrico van de Laar explores.

External Article

Doing a SQL Server Healthcheck via PowerShell

PowerShell is an ideal tool for doing health-checks of a collection of SQL Server instances, and there are several examples around, but few acknowledge the fact that individual DBAs have their own priorities for tests, and need something easily changed to suit circumstances. Omid Afzalalghom's Healthcheck allows tests to be SQL or PowerShell and requires only adding, altering or deleting files in directories.

Blogs

Capturing My Own Metrics: #SQLNewBlogger

By

A customer was trying to compare two tables and capture a state as a...

Red Flags in Your Query (T-SQL Tuesday #200)

By

When I'm looking at a query, I bet it's bad if I see... a...

T-SQL Tuesday #200: When I Look at a Query …

By

This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...

Read the latest Blogs

Forums

A Quick Second Opinion

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Second Opinion

Five Intelligent Query Processing Features in SQL Server 2022 That Quietly Tune Your Workload

By vgupta

Comments posted to this topic are about the item Five Intelligent Query Processing Features...

Checking the Error Log I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Checking the Error Log I

Visit the forum

Question of the Day

Checking the Error Log I

On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?

See possible answers