Update/Insert and speed of SQL CE

[Ian Williamson]

Greetings,

Here is my scenario: I am designing a fairly complex
application for use in the timber industry. The user will
be inputting data at a VERY high rate. For several
reasons, I am saving each row of data as focus is moved
off of it.

The problem: Between SQL CE insert/update speed and
writing to non-volatile memory speed, I am finding about a
2 second wait before the operation completes. This is
unacceptable.


I am wondering if anyone has any ideas about how I can
offload this storage wait time. Maybe save using a
background thread (but what about race conditions)? Some
over clever idea?

Thanks in advance for any ideas.


Cheers, Ian Williamson

 

[chris-s]

Could you save the entered data into an listarray/hashtable/text file/xml
file and then perform all the updates at a more 'convenient' point in the
entry/business process?

Chris

 

[Chris Tacke, eMVP]

Why wait for the insert to actually complete befoer allowing them to
continue? Spawn a worker thread and let it wait for the completion.

-Chris

 

[Rick Winscot]

Ian,

SQL CE is great for the handheld... but does have some speed issues. In
insert intensive applications, I have tied the input fields to an array. I
use the array to cache a dozen or so records at a time, and then flush the
array to the db. This is only marginally faster...

If you are using C++, a thread is your first and best choice... If you are
using .NET, threads are still a good option but thread performance is
significantly slower. You can try flat files or a pseudo transaction cache.
I wish you luck!

Rick Winscot
rickly@zyche dot com