Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

OUTPUT $action,
inserted.Year,
inserted.Month,
inserted.ProductID,
inserted.QtySold,
deleted.Year,
deleted.Month,
deleted.ProductID,
deleted.QtySold;
This, of course, performs exactly the same action it did the first time we ran it (inserting 192 rows), but
this time we get a result set back that provides information about the action taken:
$action Year Month ProductID QtySold Year Month ProductID QtySold
---------- ------ ----- ----------- ----------- ------ ----- ----------- ----------
INSERT 2003 8 707 242 NULL NULL NULL NULL
INSERT 2003 8 708 281 NULL NULL NULL NULL
INSERT 2003 8 711 302 NULL NULL NULL NULL
…
…
INSERT 2003 8 997 43 NULL NULL NULL NULL
INSERT 2003 8 998 138 NULL NULL NULL NULL
INSERT 2003 8 999 103 NULL NULL NULL NULL
(192 row(s) affected)
Chapter 7: Adding More to Our Queries
Notice that, since we only had inserted rows in this particular query, all of the data from the deleted
table is null. Things change quickly though when we run the second MERGE statement (with the same
OUTPUT clause added):
MERGE Sales.MonthlyRollup AS smr
USING
(
SELECT soh.OrderDate, sod.ProductID, SUM(sod.OrderQty) AS QtySold
FROM Sales.SalesOrderHeader soh
JOIN Sales.SalesOrderDetail sod
ON soh.SalesOrderID = sod.SalesOrderID
WHERE soh.OrderDate >= ‘2003-08-02’ AND soh.OrderDate < ‘2003-08-03’
GROUP BY soh.OrderDate, sod.ProductID
) AS s
ON (s.ProductID = smr.ProductID)
WHEN MATCHED THEN
UPDATE SET smr.QtySold = smr.QtySold + s.QtySold
WHEN NOT MATCHED THEN
INSERT (Year, Month, ProductID, QtySold)
VALUES (DATEPART(yy, s.OrderDate),
DATEPART(m, s.OrderDate),
s.ProductID,
s.QtySold)
OUTPUT $action,
inserted.Year,
inserted.Month,
inserted.ProductID,
inserted.QtySold,
211