Clever Geek Handbook

Is there a way to test the SQL generated by ADO.NET methods without resorting to database tracing / profiling?

I want to check that application A (legacy) and application B (current) are sending the same SQL to the database. Is there an easy way to check the generated SQL?

I am not too knowledgeable about minor syntax differences.

+1


source to share


1 answer


I suspect tracking is the most reliable option. Some things (like LINQ-to-SQL) let you log queries, but of course not all. But you have more security that the trail will catch everyone.



Note that "minor differences in syntax" will be very painful to compare, of course

0


source






More articles:


All Articles