SQL Server 2005 introduces the OUTPUT clause, a bit of magic that allows us to get the identity value, plus a number of other values, from an INSERT, UPDATE, or DELETE, which all have different interaction with OUTPUT. This article concentrates on INSERT.
2008-08-04
3,369 reads
Learn how to monitor database-level actions and write audit results to files.
2008-07-22
2,557 reads
In this article TJay Belt describes a process to help respond to audit requests in a timely manner
2008-06-18
2,393 reads
SQL Server 2008 February CTP introduces a new feature, SQL Server Audit. This feature facilitates auditing of Database Engine events by providing simple T-SQL statements to enable, store, and view audits on server and database objects. Part 1 of this series focuses on the server level events.
2008-06-16
2,860 reads
Tjay Belt brings us a story of how auditing was actually implemented and a discussion of why particular decisions were made.
2008-06-11
9,018 reads
Continuing with Part II of his auditing series, Gsquared takes a look at active auditing techniques for your SQL Server.
2008-06-10
10,387 reads
Auditing becomes more important every day as new requirements for data access are implemented. New author Gsquared, well known in the forums, brings us a look at types of audits and some details on passive auditing techniques.
2008-06-09
14,243 reads
Create DDL table in SQL Server 2005 to audit Data Definition Language (DDL) trigger events when DML statements run. Define DDL trigger to track SQL changes.
2008-05-15
3,467 reads
My company is just starting to look at adding functionality to retain historical data for key tables and columns for auditing purposes in many of our SQL Server databases. I have seen some of your recent tips related to triggers (Forcing Trigger Firing Order in SQL Server and Trigger Alternatives in SQL Server - OUTPUT Clause). Based on using triggers or a similar technology, what is the best way to store the historical data?
2008-04-15
5,915 reads
Auditing activities on your database servers becomes more important all the time. But ensuring that schema changes do not occur without your knowledge may be more important for a stable system. James Greaves brings us a great technique using DDL triggers for doing this.
2008-02-29
7,474 reads
By Patrick
SQL Server Audit is an efficient way to track and log events that occur...
I presented at SQL Saturday Pittshburgh this past weekend about populating your data warehouse...
By Steve Jones
A customer was asking recently about the RPO for their estate, and I showed...
Comments posted to this topic are about the item The Modern Algorithm of Chance
Comments posted to this topic are about the item Use Logic Apps To Save...
Comments posted to this topic are about the item AWS Services Using SQL for...
I have this data in my Customer table:
CustomerID CustomerName 1 Steve 2 Andy 3 Brian 4 Allen 5 DevinI run this code:
SELECT
t.CustomerID
, c.value
FROM
( SELECT
CustomerID
, STRING_AGG (CustomerName, ',') AS me
FROM customer
GROUP BY CustomerID) t
CROSS APPLY STRING_SPLIT(me, ',') c;
What is returned? See possible answers