Is there any harm (performance or otherwise) in using "Asynchronous
Processing=True" in my connection string to a sql server 2005 database
for both async db calls and non async calls? The idea behind it is
taking advantage of connection pooling, and everything seems to work
fine using the Async connection string for all calls, but I don't know
where to look for more information on this.

Thanks

That might (just might) cause some additional code paths to be entered that
would not ordinarily be called... I've never done any performance metrics on
it. I would not be surprised if it did.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Chris Becker" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Is there any harm (performance or otherwise) in using "Asynchronous
> Processing=True" in my connection string to a sql server 2005 database
> for both async db calls and non async calls? The idea behind it is
> taking advantage of connection pooling, and everything seems to work
> fine using the Async connection string for all calls, but I don't know
> where to look for more information on this.
>
> Thanks
>