The advantage of using triggers is that the same processing can occur regardless of where or how the data has been inserted, updated or deleted. In this article, we look at several examples of where and why triggers could be useful along with an example use case.
2025-09-05
2024-09-16
389 reads
2024-08-19
350 reads
2024-06-05
436 reads
2024-05-22
404 reads
2023-03-06
605 reads
2023-02-27
541 reads
Article Overview In this article, we will learn how to drop, alter, enable, and disable a PostgreSQL trigger. In the 1st part of this series, we got an overall view of database triggers, PostgreSQL-specific triggers, types of PostgreSQL triggers, and how to create a trigger with basic syntax and examples. If you haven't read it […]
2022-09-23
1,564 reads
In this article we look at how to create SQL Server triggers using Common Runtime Language (CLR) along with examples and a step-by-step guide.
2022-02-21
In this tip we look at how to create SQL Server Logon Triggers and show different examples of how this can be used.
2019-08-15
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Comments posted to this topic are about the item Where Your Value Separates You...
Comments posted to this topic are about the item Fixing the Error
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
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