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,869 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 Vinay Thakur
I wrote about TempDB Internals and understand that Tempdb plays very important role on...
By Vinay Thakur
continuing from Day 1 where we covered the history of AI and GPT family,...
By Steve Jones
It’s a day off for Redgate today. This is our annual wellbeing day, where...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers