2019-03-22
126 reads
2019-03-22
126 reads
2019-03-22
617 reads
Bad managers are everywhere, but we can improve and help them with some ideas from other companies. That's if we, as an organization, value our staff.
2019-03-21 (first published: 2015-10-19)
294 reads
This week's poll asks about virtualization in your environment. Let us know if you are moving your SQL Server to virtual machines.
2019-03-20 (first published: 2015-05-08)
195 reads
It’s just two weeks until the SQL in the City Streamed starts up again in 2019. I’m ready to travel...
2019-03-20
444 reads
2019-03-20
567 reads
The biggest government hack ever occurred recently. At least until the next one happens.
2019-03-19 (first published: 2015-10-20)
311 reads
2019-03-19
676 reads
I’m in Redmond, or Bellevue, or somewhere nearby. Not completely sure where the Microsoft MVP Summit is this week (as...
2019-03-18
551 reads
A minor disaster in Colorado reminds Steve about the need to prepare, and think about the failure points in our preparations.
2019-03-18
82 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