2022-05-18
421 reads
2022-05-18
421 reads
2022-05-11
412 reads
2022-05-04
448 reads
A major outage from Atlassian because of a bad script has Steve thinking about the challenges of recovering from mistakes. When we are making changes to portions of our data and we need to plan for mistakes to occur and ensure we can restore the data.
2022-04-22
187 reads
Continuous backup in Cosmos DB doesn't quite work as Steve would expect. He has a few comments on why it is important you know how your backup and restore system works.
2022-02-21
439 reads
2022-02-18
427 reads
2021-11-12
466 reads
2021-11-05
503 reads
2021-10-18
384 reads
Sometimes just running a backup isn't enough, especially in this era of ransomware. Steve has a few thoughts on backup strategies and recovery skills.
2021-08-09
433 reads
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
By Brian Kelley
If you don't have a plan, you'll accomplish it. That's not a good thing.
By Steve Jones
Today Redgate announced that we are partnering with Bregal Sagemount, a growth-focused private equity...
The year 2026 presents the strongest opportunity yet for people looking to earn extra...
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
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