Podcast with SQL Data Partners on Patching Best Practices
Recently, I joined Carlos L Chacon (site|@CarlosLChacon), Steve Stedman (blog|@SqlEmt), and the rest of the SQL Data Partners Podcast team...
2017-10-23
447 reads
Recently, I joined Carlos L Chacon (site|@CarlosLChacon), Steve Stedman (blog|@SqlEmt), and the rest of the SQL Data Partners Podcast team...
2017-10-23
447 reads
I will be doing a live webcast on Thursday, November 9th 2017 at 3 PM Eastern Time (8 PM UTC...
2017-10-23
443 reads
If a disaster struck tomorrow, are you ready for it? Are you sure you thought of everything? I cannot count...
2017-09-04
497 reads
A few years ago, I did a blog post series dedicated to disaster recovery (backups, restores, corruption, etc). 31 blog...
2017-08-18
470 reads
If you’ve been living under a rock, you may not have noticed how frequently SSMS is getting updated. The SQL...
2017-08-14
471 reads
It’s T-SQL Tuesday again, and this month’s host is Kendra Little (blog|@), and the excellent topic selected by Kendra is...
2017-08-08
582 reads
Join me Friday, July 21, 2017 for a day of Real-life SQL Server Performance Troubleshooting as part of SQLSaturday Columbus...
2017-06-26
708 reads
It’s time for another iteration of the blog party known as T-SQL Tuesday. This month’s theme is Shipping Database Changes...
2017-05-09
778 reads
This topic has come up several times recently, so I feel the need to blog on it. As the person...
2017-05-05
1,128 reads
Thanks to everyone who attended my presentation for the 24 Hours of PASS event on May 3rd. This iteration of...
2017-05-04
720 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