Upcoming speaking engagements
Ayyyy, matey being that today is the International Speak Like a Pirate Day I thought it was appropriate to post some future...
2012-09-19
365 reads
Ayyyy, matey being that today is the International Speak Like a Pirate Day I thought it was appropriate to post some future...
2012-09-19
365 reads
Today I am excited to join in with my #sqlfamily and participate in this months #tsql2day throw down. This month Erin...
2012-07-18
447 reads
I currently have a presentation named Performance Tuning for Pirates. This presentation goes over using several free tools to help...
2012-07-12
1,390 reads
If you work with SQL Server and live in the Harrisburg area I have some great news for you. The...
2012-07-09
657 reads
This week I have two presentations on my schedule. I get to give my Performance Tuning for Pirates presentation twice...
2012-06-28
1,387 reads
Recently, I caught my during a kickoff with a new client saying, “Hello I am John, and I love SQL....
2012-05-10
498 reads
I have a confession to make. I like to meet people who also work with SQL Server. There are so...
2012-04-17
685 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