Scribd
Upload
20 views1 page

Auditing: SQL Server Audit

The document discusses auditing in SQL Server 2008. It introduces the new SQL Server Audit feature which allows for more granular auditing than previous versions. The SQL Server Audit consists of the audit specification defining the output location, optional shutdown settings, and queue delay. It also includes server audit specifications for server-level events like logins, and database audit specifications for database-level events like schema modifications. Data Change Capture tracks changes made to data but not who made the changes, while triggers can log changes but are very expensive.

Uploaded by

divandann
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
20 views1 page

Auditing: SQL Server Audit

The document discusses auditing in SQL Server 2008. It introduces the new SQL Server Audit feature which allows for more granular auditing than previous versions. The SQL Server Audit consists of the audit specification defining the output location, optional shutdown settings, and queue delay. It also includes server audit specifications for server-level events like logins, and database audit specifications for database-level events like schema modifications. Data Change Capture tracks changes made to data but not who made the changes, while triggers can log changes but are very expensive.

Uploaded by

divandann
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Audit kae da je user mjenjao ali ne i ta je koji podatak mjenjao,kae koja tablica DATA CHANGE CAPTURE kae gdje

je je mjenjao ali ne i tko Eventualno sa trigerom na tablici , trigger pie promjene koje su se desile nad tablicom ali JAKO KOTAJU

Auditing
Auditing solutions are built to enable retrospective analysis of user activity. SQL Server 2008 introduces a number of enhancements in this regard, which will be the focus of this section. Well begin with coverage of the new SQL Server Audit feature before looking at DDL and logon triggers. Well finish with a brief look at another new feature in SQL Server 2008, Change Data Capture Novo u 2008

SQL Server Audit

In SQL Server 2005 and earlier, auditing options consisted of simple server-level logon success/failure logging, custom audits using server-side traces or SQL Profiler, or the C2 trace option. What was missing was a more granular auditing option whereby a custom audit trace could be easily created that captured specific events such as executing DBCC commands. In addition to all of the auditing options in 2005, SQL Server 2008 introduces a comprehensive new auditing model that addresses the need to easily create granular audit specifications. The new Audit feature in SQL Server 2008 consists of 3 main components: An audit, which specifies the location of the audit output (file, application, or security event log), an option to shut down SQL Server if the audit cant be written, and a queue delay setting that specifies the number of milliseconds that can pass before audit actions are processed Server audit specifications, which contain definitions of server-level audit events such as server logins Database audit specifications, which contain definitions of database level events such as schema modifications

You might also like