2008-03-09
35 reads
2008-03-09
35 reads
2008-03-09
35 reads
As DBAs we go to great lengths to ensure the security of our production data. But what happens when it moves off of a production server?
2008-03-06
32 reads
Steve Jones looks ahead to an interesting trip for the future of a couple of technical geeks.
2008-03-05
36 reads
A new technology could be a boon for database servers, dramatically increasing the amount of memory available for SQL Server.
2008-03-04
39 reads
2008-03-03
31 reads
A woman sues Best Buy for $54million. That's absurd, but her laptop is worth more than the hardware.
2008-03-02
29 reads
How important is disk encryption to you? Do you think about all those replicated or copied databases on laptops? Let us know.
2008-02-28
34 reads
SQL Server 2008 launches today and there's are additional events all across the country coming up.
2008-02-26
38 reads
2008-02-25
35 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