blocks|key|3374177|text|恐怕没有“审计功能”这回事。取而代之的是，你需要根据你的需求自己构建它。有很多方法可以做到这一点，例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3374178|每次更改审计的表中的数据时，|3374179|A触发器都会触发。这里有一个例子：http://web.archive.org/web/20071006100909/http://sqlserver2000.databases.aspfaq.com:80/how-do-i-audit-changes-to-sql-server-data.html|unordered-list-item|offset|length|3374180|using你的ORM，这里有NHIbernate的想法：Data+Auditing+in+NHibernate+and+SqlServer|3374181|3374182|entityMap|0|LINK|mutability|MUTABLE|url|http://web.archive.org/web/20071006100909/http://sqlserver2000.databases.aspfaq.com:80/how-do-i-audit-changes-to-sql-server-data.html|1|https://stackoverflow.com/questions/15917/data-auditing-in-nhibernate-and-sqlserver^0|0|0|H|3P|0|0|S|15|1|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|X|8|@]|9|@$G|Y|H|Z|1|10]]|A|$]]|$1|I|3|J|5|F|7|11|8|@]|9|@$G|12|H|13|1|14]]|A|$]]|$1|K|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]]]

I'm afraid there's no such a thing as "audit feature". Instead you need to build it yourself depending on what kind of requirements you have. There are many ways to do this, for example

<ul>
<li>A trigger fires every time data in audited tables change. An example here: <a href="http://web.archive.org/web/20071006100909/http://sqlserver2000.databases.aspfaq.com:80/how-do-i-audit-changes-to-sql-server-data.html" rel="nofollow noreferrer">http://web.archive.org/web/20071006100909/http://sqlserver2000.databases.aspfaq.com:80/how-do-i-audit-changes-to-sql-server-data.html</a></li>
<li>using your ORM, with NHIbernate
ideas here:
<a href="https://stackoverflow.com/questions/15917/data-auditing-in-nhibernate-and-sqlserver">Data Auditing in NHibernate and SqlServer</a></li>
</ul>

blocks|key|5485683|text|C2审计模式可能会为您提供一些您正在寻找的功能。虽然它不专门记录用于访问数据的SQL语句，但它将为您提供SQL+Server上成功/失败的安全请求的全面记录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5485684|http://msdn.microsoft.com/en-us/library/ms187634.aspx|offset|length|5485685|我们使用Idera+SQL+Compliance+Manager进行符合SOX的SQL审计。我不是特别喜欢它，但它似乎是业界的领导者之一，所以我认为它和任何其他产品一样好，它可以完成工作。如果您正在寻找满足一些外部需求(如Sarbanes-Oxley)，您自己的滚动可能不符合要求，您可以使用像这样的产品。|5485686|entityMap|0|LINK|mutability|MUTABLE|url|1|http://www.idera.com/Products/SQLcm/Default.aspx^0|0|0|1H|0|0|4|S|1|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]|O|$5|K|L|M|A|$N|P]]]]

C2 Audit Mode may give you some of the functionality you're looking for. While it doesn't specifically record SQL Statements used to access data, it will give you a comprehensive record of successful/failed security requests on your SQL Server.

<a href="http://msdn.microsoft.com/en-us/library/ms187634.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms187634.aspx</a>

We use <a href="http://www.idera.com/Products/SQLcm/Default.aspx" rel="nofollow noreferrer">Idera SQL Compliance Manager</a> to do our SOX-compliant SQL auditing. I don't particularly like it, but it seems to be one of the industry leaders, so I suppose it's as good as any, and it gets the job done. If you're looking to meet some external requirement (as in Sarbanes-Oxley), rolling your own might not fit the bill, and you could use a product like this one.

blocks|key|3374248|text|C2审计模式存在各种问题，而您的问题只涉及其中一个问题--性能。C2审计对性能的影响非常大，非常高。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3374249|抛开性能问题不谈，它很难管理。它不是一个“设置并忘记它”配置开关。您必须花费相当多的时间进行配置，将日志设置为转到文件，然后当您完成后，其他人可以在您后面很容易地摆脱审计文件。没有办法快速轮询您的所有服务器并确保C2审计工作正常，或者没有人丢弃文件。|3374250|SQL+Server+2008大大简化了合规性。我建议你看看SQL+Server+2008+Compliance+portal，它有一份很好的白皮书，介绍了如何配置2008年的新合规特性。2008的新审计程序使用了xEvent处理，它的性能要求大大降低，并且更易于管理。您可以使用2008的基于策略的管理来检查您的服务器，确保您正在进行审计，并在出现问题时帮助重新配置审计。|offset|length|3374251|不幸的是，一个弱点仍然是对审计输出文件的控制-坏人可以简单地删除这些文件。另一个弱点是缺乏报告-仅仅因为你有大量的审计数据并不意味着你可以用它做任何事情。您仍然需要编写自己的报告，以便分析审计数据并找出谁在做什么。这并不容易--但它比SQL2005的C2审计容易得多，而且影响小得多。|3374252|entityMap|0|LINK|mutability|MUTABLE|url|http://www.microsoft.com/sqlserver/2008/en/us/compliance.aspx^0|0|0|U|X|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

The C2 audit mode suffers from a variety of problems, and your question touched on only one of them - performance. C2 auditing has a tremendous performance impact, very high.

Setting the performance issue aside, it's very difficult to manage. It's not a set-it-and-forget-it configuration switch. You have to spend quite a bit of time doing configuration, setting up the logging to go to files, and then when you're done, someone else can come behind you and get rid of the audit files pretty easily. There's no way to quickly poll all of your servers and make sure C2 auditing is working correctly, or that someone isn't dropping files.

SQL Server 2008 makes compliance much easier. I'd recommend taking a look at the <a href="http://www.microsoft.com/sqlserver/2008/en/us/compliance.aspx" rel="nofollow noreferrer">SQL Server 2008 Compliance portal</a>, which has an excellent whitepaper on how to configure 2008's new compliance features. 2008's new auditor uses the xEvent handling which has dramatically lower performance requirements and it's much easier to manage. You can use 2008's Policy-Based Management to check your servers, ensure you're auditing, and help get auditing configured again when things break.

Unfortunately, one weakness is still control of the audit output files - the bad guys can simply delete the files. Another weakness is a lack of reporting - just because you've got gigs of audit data doesn't mean you can do anything with it. You still have to write your own reports in order to analyze the audit data and find out who's doing what. It's not easy - but it's a lot easier and lower-impact than SQL 2005's C2 auditing.

blocks|key|392039|text|C2审计模式是您正在寻找的，触发器似乎不是审计的方式。你最终用的是什么？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|392040|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

C2 Audit mode is what you are looking for, triggers seem like not the way to go for auditing. What did you end up using?

blocks|key|2307064|text|Redgate的新免费工具DLM+Dashboard使用DDL触发器将更改存储到单独的数据库，而仪表板服务将定期轮询该数据库，从而将任何性能影响降至最低。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2307065|这记录了模式更改，而不是(尚未)数据更改。|2307066|entityMap|0|LINK|mutability|MUTABLE|url|https://www.red-gate.com/products/dlm/dlm-dashboard/^0|D|D|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Redgate's new free tool, <a href="https://www.red-gate.com/products/dlm/dlm-dashboard/" rel="nofollow">DLM Dashboard</a>, uses DDL triggers to stored changes to a separate database, which is in turn regularly polled by the dashboard service thereby minimizing any performance impact.

This records schema changes and not (yet) data changes.

Did you ever use SQL Server auditing features on a production db?

How did that impact on performances, and are there differences you noticed between different versions of SQL Server.

Also how we need to enable the audit features.

Enabling Auditing feature in SQLServer 2005

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

您是否曾经在生产数据库上使用过SQL Server审核功能？这对性能有何影响?您是否注意到不同版本的SQL Server之间存在差异。以及我们需要如何启用审计功能。

问在SQLServer 2005中启用审核功能
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在SQLServer 2005中启用审核功能EN