2018-12-03
71 reads
2018-12-03
71 reads
I went to download the SSMS v17.9.1 package the other day and saw this:
I remember some issues with a C++...
2018-12-03
997 reads
Another post for me that is simple and hopefully serves as an example for people trying to get blogging as...
2018-11-30 (first published: 2018-11-15)
1,898 reads
The last 2018 edition of SQL in the City Streamed is coming in a few weeks. You can register today...
2018-11-29
354 reads
Kendra wrote a nice piece on this the other day, and I agree.
Take the Survey
The data that comes out...
2018-11-29
338 reads
2018-11-29
78 reads
2018-11-29
1,145 reads
You can register today and save for the next few days. It’s only £799 for the full SQL Bits 2019...
2018-11-28
318 reads
When you know there's a problem, it's better to solve it early rather than late.
2018-11-28
59 reads
2018-11-28
776 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...
Telp Cs: (0821)8200174 Komplek Apartemen Grand Kartini, Ruko. 18, Jl. Kartini Raya No.57, RT.3/RW.2,...
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...
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