Query Tuning, Why Bother?
Today Grant wonders why we spend so much time trying to learn about query tuning.
2022-07-23
298 reads
Today Grant wonders why we spend so much time trying to learn about query tuning.
2022-07-23
298 reads
Redgate is a great place to work for a lot of reasons. One of those has come up for me. It's time for my sabbatical. Every five years we get six weeks paid leave. Mine starts Monday. I'll still be clearing out my email (the thought of six weeks worth gives me horrors), and I'll […]
2022-07-16
140 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
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
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
In the last week I've been actively trying to join the PostgreSQL community. It's been an interesting experience. I suspect it's going to stay interesting for a while. As part of what I'm doing, I saw this excellent video from Ryan Booz, talking about joining a new community. It got me to thinking. You have […]
2022-02-12
72 reads
I'm answering a question in the forums and I spot something that crawls up my spine: ;WITH... The person was using a Common Table Expression (CTE) which requires that the preceding statement in the batch have a statement terminator, the semi-colon. However, since the terminator isn't required everywhere, lots of people don't use it at […]
2022-01-29
140 reads
We're launching into a new year and there are lots of "looking into the future" articles out there. Personally, I'm pretty jazzed for the coming year for any number of reasons (can you say "SQL Server 2022"?). However, I also get a little retrospective at times like this. Now, I'm not going to talk about […]
2022-01-08
174 reads
The Data Platform community lost a couple of people this week. Euan Garden and Dean Vargas. These were good people. They're going to be sorely missed. While I wanted to say something profound about them, I don't think I can do them justice. They were both simply good. The kind of people you want to […]
2021-12-18
214 reads
I'm writing this the day after the US holiday of Thanksgiving. Lots of things are said about Thanksgiving, positive, negative, in between. The core concept of the holiday is to take a moment to take stock of what you have. It's a good idea. Every so often, look around and acknowledge, depending on anyone's situation, […]
2021-11-27
106 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