2020-01-10
306 reads
2020-01-10
306 reads
2020-01-01
85 reads
Today is the last day of 2019, and the last day of the 2010 decade. I'm still somewhat amazed by the fact that we're entering the 2020s and we still don't really have flying cars. We're well past 2001 and 2010, and still not much space exploration, though the growth in computing power and AI/ML […]
2019-12-31
204 reads
2019-12-30
183 reads
Just one day between a holiday and a weekend, so Steve asks for the ways you escape work this summer.
2019-07-05
123 reads
2019-04-26
229 reads
Rumour has it that some grand old houses in the British Isles may be haunted. A SQL Server consultant spends a night in such a house musing over the use of T-SQL versus SSIS. The story is entirely fictitious and the article has been written pro bono and dedicated to the SQL Server community. For its interest, amusement and imagination.
2015-02-02
3,159 reads
2012-12-28
321 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