SQLServerCentral.com Articles tagged output clause

Using SQL Server's Output Clause

Mon, 26 Mar 2012 06:00:00 UT

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.

Database source control in just 5 minutes
It takes just 5 minutes to connect your SQL databases to source control. Got 5 minutes to spare? Get started now.

Dealing with Incomplete Data - A T-SQL Puzzle 1

Tue, 22 Nov 2011 07:00:00 UT

Client data received for processing may have invalid records based on processing requirements. Identifying and dealing with bad records in a specific scenario is the object of this article.

Using INSERT / OUTPUT in a SQL Server Transaction

Mon, 27 Dec 2010 07:00:00 UT

Frequently I find myself in situations where I need to insert records into a table in a set-based operation wrapped inside of a transaction where secondarily, and within the same transaction, I spawn-off subsequent inserts into related tables where I need to pass-in key values that were the outcome of the initial INSERT command. Thanks to a Transact/SQL enhancement in SQL Server, this just became much easier and can be done in a single statement... WITHOUT A TRIGGER!

Working with Queues in SQL Server

Mon, 05 Apr 2010 06:00:00 UT

This article shows sow to create a queue from a SQL table to serve each operator exactly one item from the queue that has not been picked up by any other.