Which cardinality estimator (CE) was used in my query?
SQL Server 2008 is reaching end of support this year, so upgrading your SQL Server might be on your mind....
2019-02-25
566 reads
Memory grants 7: DISTINCT (Distinct Sort)
The series is alive! It’s been a while since I last talked about memory grants. Don’t worry, I still care...
2019-02-21
397 reads
Index maintenance freebies
I didn’t expect anything for free in index maintenance. After all, it takes a lot of CPU and transaction log...
2019-02-20 (first published: 2019-01-30)
2,413 reads
Optimize for ad hoc VS single use plans
Yesterday’s post talked about single use plans. The statements I’m using are also called ad hoc queries. The alternative to...
2019-02-20
311 reads
Partitioning 5: The extra partition
So, we’ve set up a table with table partitioning on the RIGHT for CreationDate. We defined 11 partitions, and in...
2019-02-18
155 reads
Partitioning 4: Finding partitioning in DMVs and Object Explorer
Happy Friday! Today’s post will be light on the performance side and instead, I’m going to talk about how to...
2019-02-15
1,647 reads
It’s always parameter sniffing (Part 2): SET options
This is the sequel to “It’s always parameter sniffing (part 1).” In that post, we identified the stored procedure, and...
2019-02-14 (first published: 2019-01-23)
2,513 reads
Partitioning 2: Getting and measuring partition elimination
In Partitioning 1, my query searched through all 1-12 partitions. Let’s see if we can reduce that number.
Adding the partitioning...
2019-02-13
1,599 reads
T-SQL Tuesday #111 – Why I blog
This month’s T-SQL Tuesday is hosted by Andy Leonard at andyleonard.blog . Andy asks us, what is your “Why?”
So what is...
2019-02-12
683 reads
Memory Grants part 5: Query hints
Proceed with caution, if you’re thinking of using query hints. This post will specifically cover min_grant_percent and max_grant_percent.
My opinion on...
2019-02-11 (first published: 2019-01-22)
9,689 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