2013-04-02 (first published: 2008-09-11)
15,349 reads
Auditing
SqlCredit – Part 17: Exploring SQL 2005’s OUTPUT Clause
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
SQL Server Audit in SQL Server 2008 – Part 2
Learn how to monitor database-level actions and write audit results to files.
2008-07-22
2,557 reads
Automate Audit Requests
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 Audit in SQL Server 2008 – Part 1
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
Audit Database Changes in the Real World
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,022 reads
Audit Trails and Logging Part II
Continuing with Part II of his auditing series, Gsquared takes a look at active auditing techniques for your SQL Server.
2008-06-10
10,394 reads
Audit Trails and Logging Part I
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,250 reads
Using DDL triggers to audit events
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
Designing Tables for Audit Data in SQL Server
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
Blogs
T-SQL Tuesday #180: Good enough is perfect Roundup
This month, I prompted bloggers to discuss whether good enough is perfect. Thank you to all...
Using SQL Compare with Read-only Access
By Steve Jones
Recently a customer asked if SQL Compare and SQL Data Compare can be used...
Forums
Microsoft Recommendations for Update Stats?
I have an application team that is insisting on daily (and for some, weekly)...
how can i tell if our db2 driver is ms or ibm or other?
i see this in the definition of a linked server on our wh sql...
normal role member to be able to view list of other role members in his DB
Is this even possible ? Tried with grant but to no avail. [sys].[database_role_members] and...
Question of the Day
A Strange Result
What does this code return in SSMS 20 from SQL Server 2019?
select '|' + CHAR(0)+'abc' + '|';See possible answers