2018-01-29
63 reads
2018-01-29
63 reads
Kathi Kellenberger wonders what's keeping your business from upgrading.
2017-12-25
63 reads
When I began using LAST_VALUE, the results were not what I expected at all. Read on to learn the secret!
2016-06-03 (first published: 2015-04-14)
26,410 reads
2015-04-27
1,839 reads
2015-04-15
1,937 reads
2015-04-03
1,889 reads
I have several speaking events coming up, and I would love to see you there!
First of all, I'll be...
2012-07-11
1,044 reads
One of my favorite features of SQL Server Management Studio (SSMS) is the ability to run a script on multiple...
2012-03-02
2,595 reads
I drove the over 250 miles from my home in Edwardsville, IL, to attend the SQL Server 87 in Louisville,...
2011-11-02
1,319 reads
Once again I am back at home recovering from another PASS Summit. This year the attendance has exceeded all expectations...
2011-10-16
1,394 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