2017-07-11
1,185 reads
2017-07-11
1,185 reads
With SQL Server coming on Linux, some people will want to learn a bit of Linux. Or perhaps they need...
2017-07-07
1,023 reads
2017-07-07
223 reads
“Climb the mountain to see the world, not be seen by the world.” – from Tim Ford.
This past July 1 was...
2017-07-06
457 reads
2017-07-06
65 reads
I don’t think most of us need to know Linux, but if you end up managing a system, it’s good...
2017-07-05
596 reads
2017-07-05
872 reads
A holiday in the US has Steve Jones thinking about compromise and communication.
2017-07-04
52 reads
I ran across Denis Gobo’s post about working with names from Social Security cards and wanted to play with the...
2017-07-04 (first published: 2017-06-23)
2,217 reads
2017-07-04
1,177 reads
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...
The DBA life is fraught with pain. Those battles that we endure are mostly...
WA:08218154393 Jl. Jend. Ahmad Yani No.118, Sidakaya Dua, Sidakaya, Kec. Cilacap Sel., Kabupaten Cilacap,...
WA:08218154393 Jl. Ps. Pagi Raya No.9, RT.2/RW.2, Roa Malaka, Kec. Tambora, Kota Jakarta Barat,...
Comments posted to this topic are about the item A Quick Second Opinion
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