Automatically Gathering Server Information Part 3
The third part of Steve Jones's series on having SQL Server automatically report information to a DBA.
2001-04-20
11,270 reads
The third part of Steve Jones's series on having SQL Server automatically report information to a DBA.
2001-04-20
11,270 reads
It is not always possible to run a process on a set schedule. This article by Steve Jones looks at a technique for ensuring that your processes can run on whenever you need them to without any loss of data.
2001-04-18
5,347 reads
The third part of Steve Jones's series on programming and manipulating strings in T-SQL dealing with REPLACE.
2001-04-18
17,158 reads
The fourth part of Steve Jones's series on programming and manipulating strings in T-SQL dealing with numeric conversions.
2001-04-18
9,561 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