This is a two part series on how triggers work in the two latest versions of MS SQL Server. Because there are some pretty significant additions in trigger functionality from 7.0 to 2000, we'll first need to look at what the two versions have in common. The second part to this series will look at the differences between the two MS SQL Server versions.
2005-01-21 (first published: 2001-07-31)
110,884 reads
In this month's article I will cover an aspect of SQL Server that always generates a great deal of, well, shall we say "discussion"—triggers. Love them or hate them, SQL Server 2000 will change they way you think about triggers and will probably alter the way you design your applications. Specifically, this month I will dive into cascading referential integrity (RI) and the new INSTEAD OF and AFTER trigger concepts in SQL Server 2000.
2001-07-27
1,539 reads
By ReviewMyDB
A behind-the-scenes look at Day of Data Jacksonville 2026, the transition from SQL Saturday,...
You run EXPLAIN ANALYZE on a slow query, stare at the plan, and something...
By Steve Jones
la guadière – n. a glint of goodness you notice in something that you...
hi, we couldnt get our upstream data source developers to supply what is sometimes...
Are there any good articles on all the trace flags that are enabled on...
Comments posted to this topic are about the item The Data Model Matters
I run the SQLCMD utility as follows:
lcmd -S localhost -EI then type this (the 1> is the prompt):
1> select @@version goIf I hit enter, what happens? See possible answers