Hello Steffen,

> > We had 40 clients executing a scripted test of inserting 100
> > tousand records and and then reading them back (every record
> > had a fairly large BLOB embeded, altogether aproximately 750
> > MB of data)
>
> > Oh one more thing, it was also quite ingenious how the SQL
> > dev prevented the governor in MSDE with a locking startegy to
> > kick in even with 40 concurrent clients.
>
> 40 concurrent connections?
> How is this possible at all?
>
> And even if you can make MSDE use 40 connections, then this is illegal,
> right?

No, it isn't.

MSDE is NOT connection limited. It's "workload limited". That is, if
more than 5 user connections (I believe there are 2 system connections)
are executing something at the same time, then it will throttle and slow
down. So if 20 user connections are executing INSERTs, but they're
doing that serialized in such a way it doesn't reach the 5 connection
workload limit, there's nothing to be throttled.

Given the above, the possibility of having multiple users execute an
INSERT (or whatever) at the exact same time when the SQL to be
executed only takes a few milliseconds is not very high in a normal
application. Therefore, MSDE can serve applications with a much
higher user count than just 5...

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server
Upscene Productions
http://www.upscene.com