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. Keeping a connection open postpones this operation.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"An o' Neamus" <oneamus@xxxxxxxxx> wrote in message news:1191480769.967158.223910@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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: 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: SQLCE 3.0 losing data after transaction
    ... I think that not resolve the problem, because between the transaction commit ... You can also control the flush scheduling time using Connection String ... only SqlCeResultSet to get data from the database. ... inserting many rows to the database we get a "not enough memory" ...
    (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)
  • Re: Problem on INSERTING a record to database using typed datasets
    ... Thanks Kerry, its working now ..as you said i was inserting or ... updating local & not actual database file.. ... So i just modified the connection & its working.. ...
    (microsoft.public.dotnet.framework.adonet)
  • question about how to handle if row exists
    ... Since this is not supported in SQLCE ... what is the recommended way of inserting new rows in the database with a ... customer_id is a primary key ...
    (microsoft.public.sqlserver.ce)