2023-03-27
315 reads
output clause
2019-06-14
1,556 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
Upgrading SQL Server Containers on the Laptop
By Steve Jones
I don’t have SQL Server installed on my laptop. In an effort to keep...
How to Find Expensive Queries in Amazon Redshift
Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...
The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech
By gbargsley
If you've been here before, you know this blog is usually about SQL Server,...
Forums
SQL 2019 instance with AG, across 2 Windows 2016 OS servers - OSin-place upgrade
Hi all Can I get some perspective from the community please on performing in-place...
How Long is a Long I/O?
Comments posted to this topic are about the item How Long is a Long...
T-SQL Trigonometric Functions in SQL Server
Comments posted to this topic are about the item T-SQL Trigonometric Functions in SQL...
Question of the Day
How Long is a Long I/O?
In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?
See possible answers