Technical Article

Help us improve SQL Source Control

We've been working really hard on SQL Source Control, and need your input. We're currently working on suggestions from our user forum and on an updated migrations feature that supports all source control systems and works across branches. We'd love it if you could spare 10 minutes to complete this survey. If you complete the survey by Friday June 14, you could win a $100 Amazon voucher. There are two up for grabs!

SQLServerCentral Editorial

The Decision to Fail

When a disaster occurs, the response from your organization isn't always pre-determined. There are times when you might not want to failover to secondary systems, especially if you don't expect the disaster to last long. How do you decide when to fail over?

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