SQL Saturday #17 – Baton Rouge
At 5:00 AM on August 1, 2009 I was awaken by a ringing cell phone. It was Mark, the official...
2009-08-03
491 reads
At 5:00 AM on August 1, 2009 I was awaken by a ringing cell phone. It was Mark, the official...
2009-08-03
491 reads
After a long weekend of travel and speaking, I’m finally able to put my feet up and get a little...
2009-08-03
996 reads
PASS is relaunching the SQL Server Standard with a wholly new approach and format. I’ll put more out about it...
2009-08-03
714 reads
I caught this blog post, Who says technical presentations can't be engaging?, today thanks to Dana Coffey (@crazeegeekchick on Twitter). ...
2009-08-03
335 reads
In reviewing database development best practices recently I'm reminded of an attitude I've found prevalent in many development shops, that...
2009-08-03
400 reads
Its very difficult to write what all new in Sql server 2005, almost everything is new... the complete engine has...
2009-08-03
731 reads
Its been fun and fulfilling getting neck deep into the Central Texas Capitol Area Users of SQL Server again after...
2009-08-02
500 reads
I’ve done all the testing I can do for now. There were some unexpected developments that I will cover in...
2009-08-02
555 reads
One of the interesting features of LinkedIn is the ability to post a reference about a connection. If you think...
2009-08-02
875 reads
I like to blog about technical topics and community, not personal stuff. However, this is a community post. A number...
2009-08-01
622 reads
By Zikato
A cryptic message, a book cipher hidden in art provenance records, and a trail...
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...
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