What is special about 'Asynchronous Processing=true' in the connection string?

[Rob Philpott]

This allows you to execute commands asynchronously (ADO 2) using BeginXXX and EndXXX in .NET in the traditional way. But, if you want Async access, you could just use multiple threads for that (probably using seperate connections). What does this entry in the connection string actually do? Is it a case of allowing more than one command to execute at a time against a single connection?

Regards, Rob Philpott.

[Mycroft Holmes]

Absolutely no idea, never used it, never looked into it, was not even aware it existed. I have not looked at a connection string for many years. I wonder if I am missing something?

Never underestimate the power of human stupidity RAH

[Lost User]

Rob Philpott wrote:

What does this entry in the connection string actually do?

Found some good explanation (with usage scenario's) on MSDN[^];

MSDN:

In previous versions of the .NET Framework it was possible to simulate non-blocking execution by using asynchronous delegates or the ThreadPool class; however, those solutions simply blocked another thread in the background, making them far from ideal for cases where it is important to avoid blocking threads [...]

I are Troll :suss: