The Prius Update
Our second major repair will take place on the Prius, and once again it’s a cosmetic item. In fact, we’ve...
2009-03-31
1,900 reads
Our second major repair will take place on the Prius, and once again it’s a cosmetic item. In fact, we’ve...
2009-03-31
1,900 reads
I was recently asked by a co-worker on my team at work what he should do to keep up with...
2009-03-31
1,887 reads
Note: I was working on this at the Summit and then it got lost in the draft folder, so unfashionably...
2009-03-30
1,472 reads
Hey, there are probably some other blogs here letting you know that the PASS call for speakers is open right...
2009-03-30
1,344 reads
Stick with the defaults. In fact, as Andy Warren has told me many times, unless you know better and have...
2009-03-30
1,663 reads
This was an interesting year to watch the local Code Camp. Shawn Weisfeld organized it the previous two years, but...
2009-03-29
1,439 reads
SQLBits IV was held in Manchester, England, Saturday March 28th, 2009, and was attended by more than 360 attendees. This...
2009-03-29
2,103 reads
Coming Soon: Pro SQL Server 2008 Mirroring
Pro SQL Server 2008 Mirroring will be the first book dedicated to the subject...
2009-03-29
2,114 reads
Do You Support the Ancient Ones?
Are you still supporting SQL Server 2000? How about 7.0 or 6.5?
Officially, Microsoft support has...
2009-03-29
2,232 reads
A great example of how to “Tweet” poorly. This guy got fired before he started work.
Twitter is a series...
2009-03-27
1,760 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