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

Greetings,

I wrote a very simple C# console application which was designed to
give us a rough idea on the performance and reliability of SQLCE (the
source code without metrics has been posted to this group recently).
What I've found is that there are major performance and reliability
issues with SQLCE 3.0 as opposed to SQLCE 2.0. Whereas SQLCE 2.0 seems
to be fairly consistent in terms of it's memory usage and the amount
of time taken to insert rows into the table regardless of the size of
the table (to a limit, after about 300,000 records it too has major
performance issues), SQLCE 3.0 seems to slow down noticably and
continually use more memory even after a few thousand records are
inserted and actually crashes (consistently) after 25592 records are
inserted!

What gives? Based on this it would seem that SQLCE 2.0 is far
preferable for an unattended device that needs an uptime of over 30
days whilst constantly (several times per minute) inserting into the
database.

Thanks for your thoughts on this...

.

Relevant Pages

  • Re: Is it just me or are there BIG problems with SQLCE 3.0?
    ... What I've found is that there are major performance and reliability ... issues with SQLCE 3.0 as opposed to SQLCE 2.0. ... to be fairly consistent in terms of it's memory usage and the amount ... days whilst constantly inserting into the ...
    (microsoft.public.sqlserver.ce)
  • Re: SQLCE performance from .NET CF v2.0
    ... Please remember when bulk inserting is being executed against SQL CE, ... > local database functionality. ... > database technology and I am considering switching to SQLCE at the same ... > execute the prepared statement again. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Memory hog - my app and SQLCE
    ... I've done some research in to memory usage in CF 2.0 and SQLCE (mobile ... Here are my findings for future reference. ... Result: so we have a total memory usage of: 2.58 - no change. ... I added the construction of an SDF and a open connection (see ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Is it just me or are there BIG problems with SQLCE 3.0?
    ... 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. ... issues with SQLCE 3.0 as opposed to SQLCE 2.0. ... days whilst constantly inserting into the ...
    (microsoft.public.sqlserver.ce)
  • Re: Is it just me or are there BIG problems with SQLCE 3.0?
    ... We have experienced the same problems in our app which is in production. ... are uppdating the database very often by getting data from our SQL Server. ... issues with SQLCE 3.0 as opposed to SQLCE 2.0. ... days whilst constantly inserting into the ...
    (microsoft.public.sqlserver.ce)
Loading