> I think beginning with version 4.0, the CF Administrator now defaults to a
> buffer size of 0 when setting up an Access ODBC datasource. When we were
> running CF 3 we always set the buffer to 0 in accordance with Allaire's
> recommendation.
You're probably correct. We add the ODBC DB to the registry programmatically
and have been setting the buffer to the default of MS to 2048. The timeout
is set, by MS default as well, to 5.
We have since both those settings to 0 and 600, respectively. Now, we need
to go in the registry and do a search and replace on those settings and get
them all changed to the new 0 and 600 as well.
John
> -----Original Message-----
> From: Jim McAtee [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 20, 2001 1:36 PM
> To: CF-Server
> Subject: Re: Settings for Access DBs
>
>
> I think beginning with version 4.0, the CF Administrator now defaults to a
> buffer size of 0 when setting up an Access ODBC datasource. When we were
> running CF 3 we always set the buffer to 0 in accordance with Allaire's
> recommendation. I've never touched the default page timeout, which
> apparently defaults to 600. We also always uncheck 'Maintain database
> connections'. If I'm not mistaken, the buffer size and maintain
> connections
> settings are meant to combat ODBC memory leaks.
>
> We also cycle the CF Service (just the application server) every night to
> free up leaked memory. I'd be a little hesitant to do this if you were
> running a lot of e-commerce apps, since it will kill active sessions and
> dump session based shopping carts. Other than that, it only takes 3 or 4
> seconds.
>
> Jim
>
>
> ----- Original Message -----
> From: "John Cesta - Lists" <[EMAIL PROTECTED]>
> To: "CF-Server" <[EMAIL PROTECTED]>
> Sent: Tuesday, March 20, 2001 10:51 AM
> Subject: Settings for Access DBs
>
>
> >
> >
> > In the Allaire knowledgbase they propose these settings for MS
> Access DBs:
> >
> > In ColdFusion Administrator, modify every Access ODBC Datasource and set
> the
> > following (you will need to click the CF Settings button to see these):
> >
> > Buffer Size = 0 (ODBC only)
> > Page Timeout = 600 (ODBC only)
> > Uncheck Maintain Database Connections
> >
> > By a show of emails, does anyone have these settings on their
> Access DBs?
> >
> > Thanks,
> >
> > John Cesta
> >
> >
> >
> > > -----Original Message-----
> > > From: Jim McAtee [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, March 20, 2001 1:14 AM
> > > To: CF-Server
> > > Subject: Re: repair and compact DBs
> > >
> > >
> > > Also, file locks will prevent the compacting from happening,
> > > unless you just
> > > happen to hit it when the web server has no locks on the
> > > database. In turn,
> > > while you're compacting, you'll then prevent all access to
> the database,
> > > including from your web site.
> > >
> > > Jim
> > >
> > >
> > > -----Original Message-----
> > > From: Jason <[EMAIL PROTECTED]>
> > > To: CF-Server <[EMAIL PROTECTED]>
> > > Date: Monday, March 19, 2001 9:10 PM
> > > Subject: RE: repair and compact DBs
> > >
> > >
> > > >Yes you would have to have Access installed on the server or on a
> another
> > > >machine in the domain and then share the drive across so that
> > > you could call
> > > >it. Its been a while since Iv'e worked with Access - Im too
> spoiled by
> MS
> > > >SQL :)
> > > >
> > > >Make note too that you could write a script and pass it varibles for
> all
> > > >your different database items.
> > > >You could use the custom Tag CFX_SHELLEXEC and pass it
> > > parameters for each
> > > >DB from within your CFM pages and automate most of the process.
> > > >Sending a variable like (d:\inetpub\odbcsources\AccessDB.mdb)
> > > >
> > > >C:\Progra~1\Micros~1\Office\MSACCESS.EXE %1 /compact %1
> > > >-----Original Message-----
> > > >From: John Cesta - Lists [mailto:[EMAIL PROTECTED]]
> > > >Sent: Monday, March 19, 2001 7:07 PM
> > > >To: CF-Server
> > > >Subject: RE: repair and compact DBs
> > > >
> > > >
> > > >> C:\Progra~1\Micros~1\Office\MSACCESS.EXE
> > > >> d:\inetpub\odbcsources\AccessDB.mdb
> > > >> /compact d:\inetpub\odbcsources\AccessDB.mdb
> > > >
> > > >Thanks Jason,
> > > >
> > > >I guess this assumes that we have MS Access installed on the
> server. Am
> I
> > > >correct? We don't have Access installed on the server.
> > > >
> > > >> -----Original Message-----
> > > >> From: Jason [mailto:[EMAIL PROTECTED]]
> > > >> Sent: Monday, March 19, 2001 9:39 PM
> > > >> To: CF-Server
> > > >> Subject: RE: repair and compact DBs
> > > >>
> > > >>
> > > >> I think you should be able to build a batch file using the
> following
> > > >> example - obviously this depends on where your stuff is installed.
> > > >>
> > > >> C:\Progra~1\Micros~1\Office\MSACCESS.EXE
> > > >> d:\inetpub\odbcsources\AccessDB.mdb
> > > >> /compact d:\inetpub\odbcsources\AccessDB.mdb
> > > >>
> > > >> -----Original Message-----
> > > >> From: John Cesta - Lists [mailto:[EMAIL PROTECTED]]
> > > >> Sent: Monday, March 19, 2001 6:20 PM
> > > >> To: CF-Server
> > > >> Subject: repair and compact DBs
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> Does anyone know of a program that can repair and compact
> ODBC Access
> > > >> databases from the command line?
> > > >>
> > > >> Maybe it would take the DB as an argument and repair and
> compact it.
> > > >>
> > > >> John Cesta
> > > >>
> > > >>
> > > >>
> > > >
> > >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
