Post Event Notes on SQLSaturday #3
Our 3rd SQLSaturday went amazingly well due to the efforts of Brian Knight and his volunteers. Attendance for the day...
2008-05-04
511 reads
Our 3rd SQLSaturday went amazingly well due to the efforts of Brian Knight and his volunteers. Attendance for the day...
2008-05-04
511 reads
I just wrapped up a high-octane day of SQL Server community education at SQL Saturday in Jacksonville, Florida. This event,...
2008-05-04
869 reads
The purpose of The Citadel, the Military College of South Carolina, is to prepare South Carolina's citizen soldiers. It is...
2008-05-02
875 reads
A minor change for the podcasts next week. I got my wireless microphone, and I'm working with it a bit...
2008-05-02
1,920 reads
Including the parameter values to the physical report so they get printed with the business data is a best practice...
2008-05-02
535 reads
I thought they were, but I've had a bit of a debate in the forums with someone. There was a...
2008-05-02
698 reads
If you've read my blog much you'll know that I'm deeply involved in trying to figure out how to build...
2008-05-01
539 reads
I've never really been a big fan of many of the aggregation sites. As such I have never really used...
2008-05-01
713 reads
One of the things that I made a conscious effort to do last summer was make a regular effort to...
2008-05-01
728 reads
I grabbed Pro SQL Server 2005 High Availability by Allan Hirt recently to add to the library and I've been...
2008-04-30
1,367 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...
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