Re: Is it just me or are there BIG problems with SQLCE 3.0?

On Oct 6, 6:19 pm, "William Vaughn" <billvaNoS...@xxxxxxxxx> wrote:
One trick you might try is to keep a connection to the database open. If you
use the Open update Close technique, the database is compressed at the final
close. Keeping a connection open postpones this operation.


Thanks. This doesn't appear to improve performance much (if at all).
What does happen though, is that the amount of free memory on the
device gradually decreases until it's about 240Kb. It doesn't
completely run out, with 500Kb being freed before it gets a chance to
completely run out. If you then do something else on the device that
(in combination with the test program) causes the device memory to
drop to about 140Kb, then (I guess it panics) and 1Mb gets freed.
Rinse and repeat.

Same device, same program, one connection, closing the connection
often, obviously slows it down, but keeps the available memory around
6Mb.

Is this a random example that causes a need to close and reopen the
connection (to avoid a GPF)? Is the general rule to keep one
connection open for the life of the program? Will adding complexity to
the program and tables possibly change the environment such that the
GPF might not happen (this example is obviously much less complex than
the actual application's database needs)? Should we design the
application so that it occasionally closes and reopens the database
(bearing in mind it has to run indefinitely, and at least for 30
days)?

TIA

.

Relevant Pages

  • Re: ADO Connection Timeout
    ... so what happens when a connection failure forces one station to revert ... to a local database? ... Further, you *will* have contention issues, Jet does not support record ... to the central server, but you are willing to live with periods where it ...
    (microsoft.public.data.ado)
  • Re: Huge data
    ... >> connect everytime to the database to get a record or a group of records ... >> take more time than retreiving all the data and work with it offline, ... > underlying database connection each time - connection pooling takes ... > memory at a time, unless you're updating every row in the table. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Selecting from Datasets
    ... SQL provider manage Connection pooling which mean whatever sqlConnection ... instance you call it's just one virtual connection with the database managed ... > If I then have a datagrid and I only want it to display Field 1 and field ... > is no longer displayed on the page, so there shouldn't be a memory ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Oracle connections and memory usage
    ... > each connection to the database is sucking up 7MB of memory which ... > Is there anything that I can tune to improve memory usage or is there ... SG24-5511-00 Database Performance on AIX in DB2 UDB and Oracle Environments ... No. *I* am your father. ...
    (AIX-L)
  • Re: ADO Connection Timeout
    ... When the first test is run, the results are stored in the central database. ... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
    (microsoft.public.data.ado)
Loading