2023-03-27
315 reads
output clause
2019-06-14
1,555 reads
2018-08-07
940 reads
2016-09-30
1,240 reads
Using SQL Server's Output Clause
When you are inserting, updating, or deleting records from a table, SQL Server keeps track of the records that are changed in two different pseudo tables: INSERTED, and DELETED. These tables are normally used in DML triggers. If you use the OUTPUT clause on an INSERT, UPDATE, DELETE or MERGE statement you can expose the records that go to these pseudo tables to your application and/or T-SQL code.
2012-03-26
3,728 reads
Blogs
SQL Server Journey (Part 1)- Enterprise Database 2016
By Vinay Thakur
Continued thinking about my Journey blog where we have to look back at the...
Announcements from the Microsoft Fabric Community Conference
By James Serra
A ton of new features for Microsoft Fabric were announced at the Microsoft Fabric Community...
PowerShell Remoting for SQL DBAs: WinRM + SSH Guide (Updated 2026)
By SQLPals
PowerShell Remoting for SQL DBAs: WinRM + SSH Guide (Updated 2026) ...
Forums
Identities and Sequences II
Comments posted to this topic are about the item Identities and Sequences II
Using PostgreSQL as a NoSQL Store and a Search Engine
Comments posted to this topic are about the item Using PostgreSQL as a NoSQL...
Is Your Time "Free"?
Comments posted to this topic are about the item Is Your Time "Free"?
Question of the Day
Identities and Sequences II
In thinking about the differences between the identity property and a sequence object, which of these two guarantees that there are consecutive numbers (according to the increment) inserted in a single table?
See possible answers