I think I should put a few things straight before people get the wrong idea about the problem I was having with the CEDB in CE 4.2. Please read below. Apologies if there were any misunderstandings. A very helpful Microsoft person has pointed out that I have made a few mistakes on what I have written so here's to putting it right.
1. CEDB is not SQL Server CE. This I do know and I have tried to keep seperate. The current issue with CEDB does not apply to SQL CE at all since it uses a different engine.
2. Using SQL Server CE 2.0 and (upcoming) SQL Mobile:
In one of my
Blogs
I said "We are using Windows CE 4.2 not 5.0 therefore it does not support the new version of SQL Server CE. The old 2.0 version of this used the underlying CEDB engine and crashes when run from a CF Card after 4.5 days ..."
Correction: Both SQL Server CE 2.0 and SQL Mobile are supported on Microsoft Mobile Pocket PC 2003 which runs Windows CE 4.2.
The difference here is that the PPC does not turn off in hardware it does a soft shutdown
The current issue with CEDB does not apply to SQL CE at all since it uses a different engine.
Microsoft have heard a few reports of SQL CE 2.0 .sdf file becoming suspect when an end-users resets or power cycles the device while it was writing data. The following KB article describes the best practices to avoid the problem.
A Windows CE device power failure that occurs during a transaction commit may cause a SQL Server CE database to be marked suspect
(296076) - A SQL Server CE database may go into a unrecoverable state after a power failure or an explicit reset. This article discusses possible resolutions for this problem.
"http://support.microsoft.com/default.aspx?scid=kb;en-us;296076"
posted @ Monday, August 15, 2005 8:11 AM