Press Release


External Article

Help Guide the Future of SQL Compare

How changes are applied to databases differs from person to person and from organization to organization. Here at Red Gate we’re writing the next chapter for SQL Compare and we need your feedback to validate some of our ideas. To help us in this endeavour, and to enter a prize draw for one of five $50 Amazon vouchers, please complete the following survey.

2013-03-13 (first published: )

3,397 reads

Technical Article

SQL Bits XI

The popular UK conference heads to Nottingham from May 2-4, 2013. Both Grant Fritchey and Steve Jones will be speaking, along with lots of talented SQL Server professionals. Register today.

(1)

You rated this post out of 5. Change rating

2013-03-11 (first published: )

4,748 reads

Blogs

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...

Plan your 2026

By

If you don't have a plan, you'll accomplish it. That's not a good thing.

Another Change

By

Today Redgate announced that we are partnering with Bregal Sagemount, a growth-focused private equity...

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