Blogs

Technical Article

Microsoft SQL Server Licensing For Dummies..

  • Article

Don’t let the above title fool you! Have you been confused on the Microsoft SQL Server Licensing requirements? Per Processor, Per CAL, Per Core, Per Socket, Per Node – Per haps (space intended :-), we should revisit the issue again, and try to offer some assistance as you go forward in making your purchasing decisions.

(2)

You rated this post out of 5. Change rating

2011-02-04

4,848 reads

Blogs

Flyway Tips: AI Deployment Script Descriptions

By

With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...

A New Word: Fawtle

By

fawtle – n. a weird little flaw built into your partner that somehow only...

Post-quantum key exchange – Insurance policy for your packets

By

AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...

Read the latest Blogs

Forums

Where Your Value Separates You from Others

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Where Your Value Separates You...

Fixing the Error

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Fixing the Error

T-SQL in SQL Server 2025: Encoding Functions

By Steve Jones - SSC Editor

Comments posted to this topic are about the item T-SQL in SQL Server 2025:...

Visit the forum

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