blocks|key|215336|text|您可以使用log4net：http://www.nuget.org/packages/log4net/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|215337|我已经在几个大型项目中使用过它。非常有用，因为您可以指定要记录的内容/位置。|215338|由于您希望记录SQL语句，因此可以在数据访问层中放置日志。|215339|entityMap|0|LINK|mutability|MUTABLE|url|http://www.nuget.org/packages/log4net/^0|D|12|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

You could use log4net: <a href="http://www.nuget.org/packages/log4net/" rel="nofollow">http://www.nuget.org/packages/log4net/</a> 
I've been using it in a couple of big projects. Very useful as you can specify what/where you want to log. 
Since you want to log SQL statements, you can put a log in you data access layer.

blocks|key|215454|text|利用SharpPcap+API并侦听在SQL运行的端口上客户机IP和SQL+server+IP之间建立的连接。然后，您可以运行regex或类似的命令来提取SQL命令。它们中的大多数将以INSERT、UPDATE、SELECT、DELETE或EXEC开头。一旦你有了字符串，调用你所拥有的任何记录器，并根据需要进行记录。您可以将其作为服务运行，由您的应用程序启动的第二个应用程序，甚至可以在第一个应用程序的第二个线程中运行。它比ADO流水线稍微低一点，但这给了你更多的灵活性。您可以对服务器上的SQL事件探查器/+SQL跟踪收到的流量进行测试和比较，以验证它是否正常工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|215455|另一种方法是尝试修改ADO.Net代码的相关部分，并插入日志记录。像AfterThought+https://github.com/vc3/Afterthought这样的工具可能是一个选择，尽管我认为这在除了最受控制的环境之外的所有环境中都是自找麻烦的，特别是在白名单，反病毒，更新，版本控制等方面。|215456|entityMap|0|LINK|mutability|MUTABLE|url|http://sourceforge.net/projects/sharppcap/|1|https://github.com/vc3/Afterthought^0|2K|6|2R|6|2Y|6|35|6|3C|4|5X|3|2|D|0|0|1B|Z|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@$9|14|A|15|1|16]]|E|$]]|$1|F|3|G|5|6|7|17|8|@]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|H|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

Take advantage of the <a href="http://sourceforge.net/projects/sharppcap/" rel="nofollow">SharpPcap API</a> and listen for connections that are established between the client IP and the SQL server IP on the port that SQL runs. You can then run either regex or the like to extract out the SQL commands. Most of them will start with <code>INSERT</code>, <code>UPDATE</code>, <code>SELECT</code>, <code>DELETE</code> or <code>EXEC</code>. Once you have the string call whatever logger you have in place and log as needed. You can run this as a service, a second app launched by your app, or even from within the first on a second thread. It is a little bit lower down than the <code>ADO</code> pipeline but that just gives you more flexibility. You can test and compare against the traffic received by SQL profiler / SQL trace on the server to validate that it works.

The other alternative is to try and modify the relevant section of ADO.Net code and insert logging. Tools like AfterThought <a href="https://github.com/vc3/Afterthought" rel="nofollow">https://github.com/vc3/Afterthought</a> might be an option, although I think this is asking for trouble in all but the most controlled environments especially with white listing, AV, updates, version control etc.

blocks|key|215540|text|ADO.NET+Data+Tracing能为你工作吗？它插入到ETW中，从中您可以粘合您当前的日志记录系统。虽然看起来并不是很独立。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|215541|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms172144.aspx^0|0|K|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Would <a href="http://msdn.microsoft.com/en-us/library/ms172144.aspx">ADO.NET Data Tracing</a> work for you? It plugs into ETW, from which you might be able to glue your current logging system. Doesn't seem much stand-alone though.

blocks|key|215593|text|Glimpse工具提供了跟踪SQL调用(以及大量其他信息)的能力，并且正在由ASP.NET团队积极推广：http://www.asp.net/mvc/overview/performance/profile-and-debug-your-aspnet-mvc-app-with-glimpse|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|215594|entityMap|0|LINK|mutability|MUTABLE|url|http://getglimpse.com/|1|http://www.asp.net/mvc/overview/performance/profile-and-debug-your-aspnet-mvc-app-with-glimpse^0|0|7|0|1G|2M|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

The <a href="http://getglimpse.com/" rel="nofollow">Glimpse</a> tool offers the ability to trace SQL calls (along with a ton of other information) and is being actively promoted by the ASP.NET team: <a href="http://www.asp.net/mvc/overview/performance/profile-and-debug-your-aspnet-mvc-app-with-glimpse" rel="nofollow">http://www.asp.net/mvc/overview/performance/profile-and-debug-your-aspnet-mvc-app-with-glimpse</a>

I have an application that uses both Entity Framework and Dapper. I would like to provide a custom logger to log out any sql that is issued over the ado.net connection. What is the best way of doing this?

Alternately, if it's not easily possible what exactly are the difficulties?

How to capture all SQL sent over Ado.Net

服务器

我有一个同时使用Entity Framework和Dapper的应用程序。我想提供一个自定义的记录器来注销通过ado.net连接发出的任何sql。做这件事的最好方法是什么？或者，如果不容易实现，那么具体的困难是什么？

问如何捕获所有通过Ado.Net发送的SQL
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何捕获所有通过Ado.Net发送的SQLEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何捕获所有通过Ado.Net发送的SQL
EN