Automated Trigger To Require a WHERE Clause
Learn how you can build triggers that prevent an update or delete statement from being run without a WHERE clause in this article.
2013-08-09 (first published: 2011-01-25)
16,914 reads
Rahul Kumar Ghosh
Total Database Information At Your Fingertips Part - II
This article will help to get some basic information from your databases that may help you in different situations.
2011-11-24
5,561 reads
Total Database Information At Your Fingertips Part I
This article will help to get some basic information from your databases that may help you in different situations.
2011-08-16
9,290 reads
2010-12-29
2,629 reads
2010-12-17
2,780 reads
2010-12-13
2,786 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