Re: Is it just me or are there BIG problems with SQLCE 3.0?
- From: "Ginny Caughey [MVP]" <ginny.caughey.online@xxxxxxxxxxxxxx>
- Date: Mon, 8 Oct 2007 15:04:20 -0400
Hi Bill,
It would also be important to have a repro example to test against 3.5 as well.
--
Ginny Caughey
Device Application Development MVP
"William Vaughn" <billvaNoSPAM@xxxxxxxxx> wrote in message news:O9lRu1dCIHA.4956@xxxxxxxxxxxxxxxxxxxxxxx
I encourage you to get up on MSDN Connect and start pounding on the SQL CE 3.0 team to help them repro the performance and crash cases you have experienced. I have passed your comments to the dev team directly but did not get much more than "It seems to run faster for us...". Since they have not shipped I think it would make sense for everyone to get these issues resolved.
hth
--
____________________________________
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:1191824843.761884.215690@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxOn 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. The database was kept open for the entire test run. Another
poster (in this or another thread I started on this subject),
suggested closing the database occasionally to get around the problem
we were seeing (ie. the database engine causing a GPF). As SQL CE 2.0
doesn't crash and is much faster, we've elected to use this version as
opposed to SQL CE 3.0.
At this point, the only unanswered question we have is whether there
are any reasons at all (given that performance and reliability are
severely degraded) why we should even consider using SQL CE 3.0?
TIA
.
- References:
- Is it just me or are there BIG problems with SQLCE 3.0?
- From: An o' Neamus
- Re: Is it just me or are there BIG problems with SQLCE 3.0?
- From: William Vaughn
- Re: Is it just me or are there BIG problems with SQLCE 3.0?
- From: An o' Neamus
- Re: Is it just me or are there BIG problems with SQLCE 3.0?
- From: William Vaughn
- Is it just me or are there BIG problems with SQLCE 3.0?
- Prev by Date: Re: Is it just me or are there BIG problems with SQLCE 3.0?
- Next by Date: Re: Is it just me or are there BIG problems with SQLCE 3.0?
- Previous by thread: Re: Is it just me or are there BIG problems with SQLCE 3.0?
- Next by thread: Re: Is it just me or are there BIG problems with SQLCE 3.0?
- Index(es):
Relevant Pages
|
Loading