SQL Server 2025 Backup Compression Algorithm
Learn about the new ZSTD compression algorithm in SQL Server 2025.
2025-12-29
1,766 reads
Learn about the new ZSTD compression algorithm in SQL Server 2025.
2025-12-29
1,766 reads
Learn how backup and restore work in Azure SQL Hyperscale in this next level in the stairway series.
2025-12-17
710 reads
2025-10-27
1,170 reads
There are multiple reasons for no full backup: corrupted backups, taking too much time to restore, etc. In this post, I want to show an alternative for these cases, an ace up one’s sleeve, that you can use to recover data.
2025-06-23
Who among us hasn't deleted a production data file? Steve hopes most of us have not.
2025-05-30 (first published: 2025-05-12)
205 reads
2025-03-28
1,143 reads
2025-03-24
729 reads
2025-03-10
371 reads
In this article, we look at how to create a SQL backup to network share or restore a backup from a network share.
2025-02-28
2025-02-24
340 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