I am an amateur radio operator. In the US this is commonly referred to as a ham, or a ham radio operator. My call sign is KC1KCE, as issued by the US government through the FCC. And yeah, I can hear you now, a ham is the geek equivalent of a cross-fitter. How do you […]
2023-01-20 (first published: 2023-01-14)
146 reads
Happy New Year! You're going to be seeing a lot of summaries for 2022 and predictions for 2023 around this time of year. I'm not writing one of those. You'll also see people calling for new years resolutions and the like. I'm not going for that either. Nope, let's keep it simple. It is a […]
2022-12-31
59 reads
If you're an experienced, knowledgeable, seasoned (I won't say old), SQL Server data professional, and you choose to use Trace Events (Profiler), more power to you. That's it. That's all I have to say. Do what you think best. I'm never, ever (again), going to second guess you. Further, my apologies for ever having done […]
2022-12-10
195 reads
Very excited to take part in my third #PGSQLPhriday blogging event, even more so because it’s a topic that’s quite near and dear to my heart, community. To say...
2022-12-02
22 reads
Just a quick post to let you know that there’s a great sale right now at Springer on my brand new, completely rewritten, query performance tuning book. Get your...
2022-11-21
51 reads
If you’re interested in getting a digital copy, my brand spanking new book is now available here. It’s in the intro, but let me tell you a little bit...
2022-11-11
244 reads
It’s time again for the another PGSQL Phriday, this time, the question has been asked: How do you do PostgreSQL backups? Honesty up front. I’m very much just beginning...
2022-11-04
12 reads
I spend a lot of time in the forums on various web sites, trying to assist people with getting help online. It’s shocking how hard they make it. Let’s...
2022-11-02 (first published: 2022-10-24)
146 reads
I may have occasionally talked about the importance of Query Store, but today I want to emphasize just how much Microsoft is weaponizing query store. Of course, I don’t...
2022-10-31
8 reads
PASS Data Community Summit is coming up like an out of control freight train. Another couple of weeks and it'll be here. I'm excited about it every year and I really hope to see you there. Please, consider this a personal invite to say hi if you see me around. I'm bringing all this up […]
2022-10-29
127 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