"Dan Brussee" <db******@nc.rr.com> wrote in message
news:ce********************************@4ax.com...
This may not be true, but I heard that the "throttling" was basically
a mechanism to artificially slow the server down as it went over X
number of concurrent users... not that it would just stop working.
It's not actually the number of concurrent user, it's concurrent operations.
From
http://msdn.microsoft.com/library/de...2000webapp.asp
<quote>
Understanding the Workload Governor
All versions of SQL Server 2000 (including MSDE 2000) support up to 32,767
connections per instance ...[snip] ... More importantly for your application
designs, MSDE 2000 employs what is known as a concurrent Workload Governor.
The effect of the governor is to slow certain operations down by stalling
user connections for a few milliseconds whenever there are more than eight
concurrent operations. Some system-generated events in the database engine
count against this eight-operation limit, so the governor may kick in even
when your application code requests fewer than eight operations. The key is
concurrent operations, such as executing a query. This is not the same as
concurrent users. In most applications, there is a certain amount of user
"think time," where a live connection to the server exists, but the user is
not actually performing a task that accesses the database. The actual number
of concurrent users can be much higher.
</quote>
I'm just wondering what this means in practice.
Martin Harran