SQLServerCentral Editorial

The Data Professional Social Graph

Two weeks ago, I had the opportunity to hear a keynote by Vik Fearing at Swiss PGDay 2023. He talked about Property Graphs and the Graph Query Language (not to be confused with GraphQL), a recent addition to the SQL:2023 standard. The discussion was mostly theoretical in nature because only Oracle has a current implementation […]

(1)

You rated this post out of 5. Change rating

2023-07-08

99 reads

SQLServerCentral Editorial

Same Language, Different Words

I had to come to the Redgate office in Cambridge this past week for a department onsite. As a result, my wife and I were able to come early for a few days adventuring together, the first trip we've taken by ourselves in nearly seven years. As a large family with six kids, it takes […]

You rated this post out of 5. Change rating

2023-06-17

134 reads

SQLServerCentral Editorial

Moore's Law: Navigating the Pace of Technological Change

Technology has always been a driving force in shaping our world, propelling us forward into new realms of innovation and progress. One of the most famous concepts in technology is Moore's Law, which suggests that the number of transistors on a microchip doubles approximately every two years, leading to exponential increases in computing power. In […]

(1)

You rated this post out of 5. Change rating

2023-04-15

150 reads

SQLServerCentral Editorial

The Human Factor

A week ago I was in Pasadena attending the SCaLE 20x conference, a gathering of many different open-source communities discussing the technologies and platforms that draw them together. I was fortunate enough to hear some excellent presentations on PostgreSQL and give two talks as well. After the first round of talks on Friday morning a […]

You rated this post out of 5. Change rating

2023-03-18

91 reads

SQLServerCentral Editorial

With the Rise of AI Chat, are Experts Still Needed?

As I looking at the feed of technology stories this week, two things jumped out at me. First, Valentine's day happened to fall on the monthly release day for Microsoft updates and feature previews. If you work with Azure services, specifically in the data platform space, there are a lot of update announcements to work […]

You rated this post out of 5. Change rating

2023-02-18

176 reads

SQLServerCentral Editorial

The Power of Community in Times of Uncertainty

The last two weeks have brought a (seemingly) daily deluge of difficult news in the tech sector. Microsoft, Google, Facebook, and Amazon have all had significant layoffs with many friends in the #SQLFamily and data community being impacted. In times of uncertainty and heightened anxiety, it’s essential to have a group you can turn to […]

(3)

You rated this post out of 5. Change rating

2023-01-21

102 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