[AccessD] SQL Server Express - true skinny

Drew Wutka DWUTKA at Marlow.com
Mon Sep 13 13:52:39 CDT 2010


Exactly.  Which is part of the premise of the bound/unbound debate.
With unbound forms, where data is written in a split second chunk, the
stability of much higher user volume goes up tremendously!

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Friday, September 10, 2010 2:46 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] SQL Server Express - true skinny

Dan,

 That is more or less true, but the real bottle neck with a JET based DB
has
never been .LDB file operations.

 With JET, all processing is on the client side.  The server acts as
nothing
more then a file share. 

 The trick with keeping a connection open to the BE avoids the repeated
closing/opening of the LDB and DB files and all the associated overhead
with
removing/adding an active user under JET.  Some apps benefit from that,
other not because they already maintain a connection one way or another.
The problem can be further compounded if the server has OPLOCKS on
(which
allows client side caching of files).  JET doesn't need this as the
cache is
already on the client side.  So it's simply a wasted effort on the
servers
part.  And by default, OPLOCKs is enabled on Windows servers.

 The real restriction of JET is just one of stability.  With no server
side
process to perform a rollback if a disconnect occurs, anytime that
happens
in the middle of write operations your fair game for corruption.   So by
the
time you get past 30 or 40 stations, it's just hard to keep the
environment
stable.

 To prove that point, you can easily run a read-only/reporting JET based
app
with 200+ users without issues.

 It's not an issue of performance, but one of stability.

Jim.
The information contained in this transmission is intended only for the person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI Business 
Sensitive material. If you are not the intended recipient, please contact the sender 
immediately and destroy the material in its entirety, whether electronic or hard copy. 
You are notified that any review, retransmission, copying, disclosure, dissemination, 
or other use of, or taking of any action in reliance upon this information by persons 
or entities other than the intended recipient is prohibited.





More information about the AccessD mailing list