SELECT *

SELECT * feels convenient, but in SQL Server it bloats I/O, burns network bandwidth, blocks covering-index usage, and makes code brittle when schemas change. Specify only the columns you...

2025-10-02

42 reads

Blog Post

SQL Server is Slow, part 3 of 4

In parts 1 and 2 of this series, we’ve gathered info and done the triage just like anyone in almost any industry does At this point you’ve: Defined what...

2025-10-27 (first published: )

1,739 reads

Blog Post

Back in the EU

I flew to Amsterdam last night and hopefully by the time this publishes I’ll be at my hotel, catching up on messages and prepping for another Simple Talk Podcast...

2025-09-29

17 reads

Blogs

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

Reflections on the Life of a DBA

By

The DBA life is fraught with pain. Those battles that we endure are mostly...

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