That's right.. so actually, you COULD use 5 different instances of COM ADO
Connections and be quite sure about it..
Another thing is that performance is only degraded, when you exceed the
threshold. So you might not have to be so shy about going over the limit
from time to time!
Don't forget that there are other constraints though - such as the 2Gb limit
which you might want to keep in mind!
> That is good that they are serialized so my design will work.
> So just to clarify, idle connections should not have any bearing. For
> instance, you could have 100 connections but as long as only 5 batches (in
> separate connections) are run simultaneously, there should not be any
> performance degradateion.
> > Hi Jeff..
> > It has very much to do with concurrent db connections.
> > Although, to answer your qn directly, if 5 threads share a pointer to
> > same COM ADO Connection, their batches (more accurately - "Commands" in
> > context) will be serialized - one after the other.
> > You can observe this behaviour using the profiler.
> > If you can live with this design in your VB app, you should be ok..
> > HTH
> > Cheers,
> > Greg Linwood
> > > I have read the manual about the 5 concurrent batches:
> > > A concurrent workload governor limits the performance of the database
> > engine
> > > in these two editions. The performance of individual Transact-SQL
> > is
> > > decreased when more than five batches are executed concurrently. The
> > amount
> > > each batch is slowed down depends on how many batches over the
> > > limit are executing concurrently, and the amount of data retrieved by
> > > individual batches. As more batches are executed concurrently, and as
> > > data is retrieved by each batch, the more the governor slows down the
> > > individual batches. You can use the DBCC CONCURRENCYVIOLATION
> > > report how often the concurrent workload governor is activated. For
> > > information, see DBCC CONCURRENCYVIOLATION
> > > Does this have anything at all to do with concurrent db connections?
> > > If you share one connection among 5 or more threads in ADO are your
> > > going to run into this if they execute something all at once.
> > > Thank You,