Demystifying the use of CASE in an ORDER BY statement
Chuck Hoffman exposes the mysteries of getting CASE statements to work in dynamic ORDER BY statements.
2015-06-05 (first published: 2012-04-26)
26,520 reads
Chuck Hoffman
Selecting from hierarchies like Managers and Employees
Chuck Hoffman shows a technique using sets for selecting records from hierarchies such as Manager / Employee structures.
2012-05-03
9,727 reads
TSQL TestBits function for rapidly testing multiple switch settings
Are multiple binary switches becoming hard to manage? The TestBits function can help with that.
2012-04-09
4,224 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