Posted by Erland Sommarskog on 08/29/07 21:38

(raymond_b_jimenez@yahoo.com) writes:
> I've noticed in my .NET application (with ADO) that whenever a query
> is done to SQL Server, a query executing
> SET NO_BROWSETABLE ON
> is done before.
> This has an huge impact on performance, as the round-trip to the
> server takes the same time as the correct query. I believe that if
> "SET NO_BROWSETABLE ON" wasn't executed, performance would almost
> double and network traffic would be reduced.
> I've tried to find a reasonable answer on the net for this, but
> haven't managed. Has someone noticed this and knows how to correct it?

Which .Net Data provider do you use?

ADO (the one is not worthy to be called Classic, but which is not .Net)
spits this out, and it is about impossible to stop.

SqlClient does not send this by default, if you use CommandBehaviour.KeyInfo
it does.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]