>When parameters are used with SQL Server ODBC driver, they end up to be passed to the sp_executesql with a query itself. I don't know what .NET provider does. That's why I suggested to use SQL Server Profiler to see what actual SQL statement sent to the SQL Server from your application. It could be the sp_executesql as well.

Yes, correct, SQL Profiler shows everything in sp_executesql approach. I guess I will adjust the data class of my framework to use it back and I will see how it goes today with more tests I will do. It might not be that much on a per transaction basis to save one hundred of a second, but at large scale, this might mean that we could support up to thousands of additional hits per day within the same infrastructure.

BTW, I was just curious to know what develpment platform you are using or is it mostly some DBA stuff at the server level?

Thanks