2019-04-30
380 reads
2019-04-30
380 reads
Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers. I saw a post recently where someone needed...
2019-04-30 (first published: 2019-04-17)
449 reads
2019-04-29
747 reads
Tomorrow is the SQL in the City Summit in London. Right now I’m in a Heathrow airport hotel, finalizing some prep for the event. I have to run a...
2019-04-29
14 reads
2019-04-29 (first published: 2015-09-14)
321 reads
2019-04-27
164 reads
Maybe we can get Chris Spalton to do some of these for all our events? I really like it. Just a few days until SQL in the City Summit...
2019-04-26
55 reads
My default setup for a few years is to only use named instances, usually with a standard SQL2014 or SQL 2016 as the name of the instance. Recently, I...
2019-04-26 (first published: 2019-04-22)
1,981 reads
2019-04-26
230 reads
2019-04-26
494 reads
By Steve Jones
A customer was trying to compare two tables and capture a state as a...
By Zikato
When I'm looking at a query, I bet it's bad if I see... a...
By Steve Jones
This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...
Comments posted to this topic are about the item A Quick Second Opinion
Comments posted to this topic are about the item Five Intelligent Query Processing Features...
Comments posted to this topic are about the item 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