SQL Server Upgrades: In-Place or New Server?
This isn’t a religious debate. I have a client right now debating how to handle SQL Server upgrades across all of their dev and test environments. And it’s...
2025-12-31
Kevin3NF
- Interests: Cycling, family, sci-fi, DBA stuff
Data Conferences – Worth Every Dollar
Some of the best career enhancers you can buy. Why I Go to Conferences I go for two big reasons: Learning from the best. The folks teaching at...
2025-12-01 (first published: 2025-11-12)
271 reads
SQL Server Reliability: Clearing the Fuzzy Thinking
The terminology around reliability is a mess If you’ve ever said, “We’re covered, it’s replicated,” you’re in good company. SQL Server is a massive, 35+ year-old product that...
2025-11-19
15 reads
SQL Server Alerts
Don’t Let Trouble Sneak Up on You Most SQL Servers run quietly. Until they don’t. By the time someone notices an application outage or a failed backup, you’re...
2025-11-03 (first published: 2025-10-15)
324 reads
SQL Server Versions: Out With the Old, In With the Supported
If your production SQL Servers are still running 2016 (or older) you’re basically banking on inertia. Sure, it’s been stable. But that doesn’t guarantee it’ll stay safe or compliant....
2025-10-29
25 reads
SQL Server is Slow, part 3 of 4
In parts 1 and 2 of this series, we’ve gathered info and done the triage just like anyone in almost any industry does At this point you’ve: Defined what...
2025-10-27 (first published: 2025-10-01)
1,719 reads
SQL Server Migration Overview
It’s Not Just Backup / Restore At some point every company faces it: the SQL Server that’s been quietly running for years is due for retirement. Maybe the hardware...
2025-10-22
16 reads
SQL Server Is Slow (part 1 of 4)
How should you respond when you get the dreaded Email/Slack/Text/DriveBy from someone yelling at you that SQL Server is slow? Stop. Don’t Open SSMS Yet. You’ve heard it...
2025-10-08 (first published: 2025-09-17)
402 reads
“SQL Server Is Slow” Part 4 of 4
Parts 1, 2 and 3 got you to the (SQL) engine room. Now we use community-trusted tools to find what’s going on, fix it safely, and hopefully keep it...
2025-10-07
188 reads
SQL Server Is Slow – Part 2 of 4(?)
The 10-Minute Outside-In Triage Don’t Blame SQL First It’s 9:05 AM and your helpdesk lights up: “The SQL Server is down. Nothing works.” By 9:07, everyone is staring at...
2025-09-24
24 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