Accessibility is not just about slides
Although I don’t write about it much on this website, I am on the autism spectrum, and I have ADHD. I need to sit at the front of a...
2021-08-04
16 reads
Although I don’t write about it much on this website, I am on the autism spectrum, and I have ADHD. I need to sit at the front of a...
2021-08-04
16 reads
This post is part of the series I kicked off here. You can read my post about captions here. Let’s talk about slides! Many of us are familiar with...
2021-07-28
18 reads
Next week on Wednesday 28 July 2021, I will be presenting a brand-new session titled “How SQL Server stores that data type” for the free EightKB virtual conference. I’ve...
2021-07-21
19 reads
My user group, the Calgary Data User Group, has been recording videos since April of this year, so at the time of this writing we have just two videos...
2021-07-14
12 reads
Today I want to write about the community that brought us all together. The community that got this very website on your radar. The community that got many of...
2021-07-07
11 reads
In early 2011 Jes Borland invited us to write about aggregations: I want to hear how you solved business problems with aggregate functions. I want to see your cool...
2021-06-30
42 reads
It has been some time since I last wrote about Azure SQL Database. Although it has been more than three years since SQL Server 2017 was released, Microsoft have...
2021-06-23
57 reads
If you’d like to check out the previous instalment in this series on storing dates and times, click here. I avoided mentioning this data type because I didn’t think...
2021-06-16
32 reads
Whenever I restore a database — especially one I obtained outside of my regular environment (for example a customer database, a development database, or even a sample database like...
2021-06-09
46 reads
Last week I wrote about recovering data after an unplanned outage, and this week I’m contemplating a thing that would be considered bad in those circumstances as well as...
2021-06-02
12 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