Undocumented use of the Columns_Updated() function
Q I need an easy way to see if a delete transaction has fired a trigger. Do you have any...
2007-08-01
627 reads
Q I need an easy way to see if a delete transaction has fired a trigger. Do you have any...
2007-08-01
627 reads
Some of you younger DBA’s out there may not know who Neil Sedaka is or remember his poignant words "Breaking...
2007-07-03
611 reads
Breaking Up is Easy to DoHardIt's nice to be able to package a process into a single, tidy, elegant query,...
2007-07-03
601 reads
No, I'm not going to keep making corny references to war and being a soldier. But in many ways, we...
2007-06-29
1,336 reads
The active SQL Server error log is one of the first places people look when there is a problem. For...
2007-06-29
1,593 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