Ensuring Each Client has a Full Set of Key-Value Pairs
In this piece, we find out about a business issue that can occur when using key value pairs in your database to describe information about other entities.
2018-07-10
601 reads
data integrity
Find and Remove Duplicate Records SQL Server
Learn a quick method to find and remove duplicate records in your SQL Server tables.
2016-02-01
9,764 reads
Why is data integrity important?
Why should I care and why should the database enforce it? This article from Jamin VanderBerg gives some reasons why the database is the place to enforce rules that ensure integrity.
2010-08-30
3,997 reads
Blogs
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
A New Word: Fawtle
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Forums
Where Your Value Separates You from Others
Comments posted to this topic are about the item Where Your Value Separates You...
Fixing the Error
Comments posted to this topic are about the item Fixing the Error
T-SQL in SQL Server 2025: Encoding Functions
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
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