Thank You Kevin!
I don’t think I’m going too far out on a limb to call Kevin Kline a friend. I’m extremely humbled and honored that I can say that. Kevin is...
2022-07-06
18 reads
I don’t think I’m going too far out on a limb to call Kevin Kline a friend. I’m extremely humbled and honored that I can say that. Kevin is...
2022-07-06
18 reads
Most of the time when I talk about or demo Extended Events, I spend more time talking about query tuning (I have a problem). However, there are tons of...
2022-07-05
146 reads
I've just finished working in my fourth shared work space. I am not a fan. The endless hallways with all these little glassed in rooms where I can see everyone, and everyone can see me, are not my favorite places. I can see white boards with content that maybe I shouldn't be seeing. There are […]
2022-06-25
160 reads
Hello all. I know most of you are still working within SQL Server. However, a few of you are become more like me, hybrid data managers, working in more...
2022-06-13
4 reads
As I’ve been working more with PostgreSQL, I’ve found that I’m basically pretty happy just issuing SQL commands to get work done. However, it’s handy to have an actual...
2022-06-06
4 reads
This week I was honored to be able to attend, and present a session at, SQLDay in Wroclaw Poland. I fell in love with Poland the very first time I attended this event, so I look forward to any time I can go again. This year, Pavel Potasinski presented the keynote: The Evolution of the […]
2022-05-14
125 reads
For the longest time, we didn’t have one of the most useful tools for monitoring SQL Server behavior, but I just found out that, indeed, you can use Extended...
2022-05-11 (first published: 2022-05-02)
192 reads
TLDR: There ain’t one. I was privileged last week to be able to present a couple of sessions at the SQL Server and Azure SQL Conference (great event, I...
2022-04-18 (first published: 2022-04-11)
603 reads
Two years ago at the start of the pandemic, I wasn’t feeling great about things. I saw that quite a few others weren’t all that thrilled about how things...
2022-04-04
35 reads
This week was the MVP Summit. As was the case for the last couple of years, the event was entirely virtual. We were shown a bunch of new and interesting things by Microsoft. We were able to talk to each other and to the engineers at Microsoft. I'm honored that I've been an MVP and […]
2022-04-02
42 reads
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Comments posted to this topic are about the item Where Your Value Separates You...
Comments posted to this topic are about the item Fixing the Error
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers