🚀 go-pugleaf

On Mon, 24 Apr 1995 rick_treese@RESGATE2.RCH.GS.COM wrote:

>      We have several Client VB apps hitting up against SQL Server, and
>      currently we keep these client applications connected to the server
>      during the entire time they are loaded (basically all day).  Since the
>      apps make a maximum of about 50 quick calls to the server each day, is
>      it better to have them dynamically log in and out as they need to use
>      the server, or is this a bad way of managing connections?  Is there a
>      formula generally used (i.e. if the app makes more than X calls in X
>      amount of time, keep it connected , otherwise log/out on the fly), or
>      a standard way of handling this??
>

There's a lot of lattitude here.  Different people handle this
differently.  When I was at a large broker/dealer, we used MSSQL for the
back end of a Marketing system used by 400+ users.  The apps were
written to log in, do their stuff and log out.  We never got over 9 or
10 simultaneous users.  On a limited license and equipment budget, this
is a very viable way to go.  If you've only got a couple of users, then
keep doing it the way you're doing it.  But you can't roll that out to a
larger user community without a bigger license, and maybe more memory.

-- Paul. (flint@io.org)