2008-02-18
31 reads
2008-02-18
31 reads
2008-02-17
42 reads
There are many ways to accomplish a task in SQL Server, and almost every technology. But too much choice might not be the best thing for beginners.
2008-02-12
48 reads
Using the Identity Property might be one of the more debated features of SQL Server.
2008-02-09
42 reads
Windows 2008 RTMs, a change from the SQL Server support team, and a Jump Start for Katmai.
2008-02-09
38 reads
Steve Jones asks about the disclosure of source code in legal proceedings.
2008-02-07
44 reads
Corporate management often asks for feedback and buy-in with their ideas and programs. Why don't they get it?
2008-02-05
44 reads
Employee compensation is more than just salary. Steve Jones talks about how you might look at building more effective compensation plans for workers.
2008-02-04
40 reads
Less CIOs are reporting to CEOs this past year. Is that a problem? Steve Jones offers some comments.
2008-02-03
37 reads
2008-01-31
46 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