It’s always parameter sniffing (part 1?)
This is a blog post about a perennial issue. Have you ever had a call in the middle of the...
2019-01-28 (first published: 2019-01-16)
3,029 reads
My alternative to sp_WhoIsActive
I use sp_WhoIsActive a lot. I’m extremely grateful for Adam Machanic writing it. It has tons of options that let...
2019-01-28
5,059 reads
Memory Grants part 6: Memory used in aggregate functions (Min/Max/etc)
So far in this series, I’ve been focusing on the Sort operator. It’s pretty easy for demos since I can...
2019-01-25
677 reads
The Execution plan comparison feature (in SSMS)
Did you know that you can compare two execution plans in SQL Server Management?
It’s really cool. I use it a...
2019-01-25
990 reads
SQL Server Monitoring: What to start measuring
So you’ve got a SQL Server that you want to monitor. What should you monitor? In my opinion, at bare...
2019-01-22 (first published: 2019-01-14)
2,655 reads
Memory Grants part 4: The Resource Semaphore
Part of query memory grants, part 4! This post will cover the wait type RESOURCE_SEMAPHORE briefly, but the focus is...
2019-01-21
1,031 reads
New page on this blog: Contact Me
This is not a technical post! Just wanted to say that I set up a public email address for this...
2019-01-19
132 reads
When the query plan hash is deceptive
When you’re querying the plan cache, you need to know the four primary objects: the query hash, query plan hash,...
2019-01-17
756 reads
Execution plans: RetrievedFromCache
I first came across the value for RetrievedFromCache when I was reading a confusing execution plan. At first, I thought...
2019-01-11
684 reads
Why is the query hash so useful?
An example of how I use the query hash
I wrote a blog on what the query hash is, right here....
2019-01-10
6,451 reads
Blogs
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
A New Word: Fawtle
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Forums
Where Your Value Separates You from Others
Comments posted to this topic are about the item Where Your Value Separates You...
Fixing the Error
Comments posted to this topic are about the item Fixing the Error
T-SQL in SQL Server 2025: Encoding Functions
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Question of the Day
Fixing the Error
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