Does sqlce 3.0 surport the wince 4.2?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Tommy - 20 Oct 2007 06:17 GMT

I develop my app on the wince 4.2 and sqlce 2.0 using evc 4.0. When I
found the size of the db files cannot shrink automaticlly I searched
for help through this group and I got the answer was the size of db
files with sqlce 2.0 does not increase after any deleting of rows. Now
I have to upgrade my sqlce version to 3.0. But I am wondering if the
sqlce 3.0 surport the wince 4.2 and what I should do.

Does anybody know whether the 3.0 edition is able increase the db
file's size after some deleting action.

And where can I get the install file for the wince 4.2 and the desktop
tie.

Does anybody got the same truble? If you met, can you please tell me
your solution?

Thank you for your sugestions or clues.

Reply to this Message

ErikEJ - 21 Oct 2007 11:39 GMT

SQL CE has an autoshrink feature, I guess this is what ou are requesting.
(I will kick in when the last connection to the database is closed).

For SQL Compact cab files for CE 4.2 see:
http://support.microsoft.com/kb/934386/en-us
and
http://support.microsoft.com/kb/924811/
(depending on your platform)

Signature

Erik Ejlskov Jensen, Mobile App Dev MCTS
Check out my SQL Compact blog at
http://erikej.blogspot.com

>I develop my app on the wince 4.2 and sqlce 2.0 using evc 4.0. When I
> found the size of the db files cannot shrink automaticlly I searched
[quoted text clipped - 13 lines]
>
> Thank you for your sugestions or clues.

Reply to this Message

Tommy - 22 Oct 2007 09:03 GMT

ErikEJ:
Thanks a lot for your response. Could you tell if there is some
methord to fix the un_shrinkable bud for SQL CE 2.0?
I have read the articles you give me, but It seems to describ how to
fix the using SQL CE 2005 for wince 4.2.
We wanna keep using SQLCE 2.0 if there is no method to fix this
problem because we have developed our app on it.
And I am afraid the transport of SQLCE version will cause some
problems more complex.

> SQL CE has an autoshrink feature, I guess this is what ou are requesting.
> (I will kick in when the last connection to the database is closed).
[quoted text clipped - 26 lines]
>
> - Show quoted text -

Reply to this Message

Erik Ejlskov - 22 Oct 2007 17:14 GMT

The only way to shrink 2.0 databases is to perform a Compact.
Please note SQL CE 2005 = SQL CE 3.0

Signature

Erik Ejlskov Jensen
- see my SQL Compact blog at
http://erikej.blogspot.com

> ErikEJ:
> Thanks a lot for your response. Could you tell if there is some
[quoted text clipped - 36 lines]
>>
>> - Show quoted text -

Reply to this Message

Tommy - 31 Oct 2007 04:09 GMT

Erik:
Thank you for your responding. I got a truble that we dont using
the .net CF on our platform
and access to the db through oledb interfaces. So does that mean we
dont have way to compact
the db files unless we install a CF on our WINCE 4.2?
Please give me your suggestions.
On Oct 23, 12:14 am, "Erik Ejlskov" <ejlskov_nos...@hotmail.com>
wrote:

> The only way to shrink 2.0 databases is to perform a Compact.
> Please note SQL CE 2005 = SQL CE 3.0
[quoted text clipped - 49 lines]
>
> - Show quoted text -

Reply to this Message

ErikEJ - 31 Oct 2007 19:38 GMT

Both AutoShrink and CompactDatabase are available to native developers via
the OLEDB interfaces, according to SQL Compact 2005 books online:

DBPROP_SSCE_AUTO_SHRINK_THRESHOLD
The percent of free space in the database file that is permitted before
autoshrink begins. A value of 100 disables autoshrink. If not specified, the
default value is 60.

HRESULT CompactDatabase(BSTR SourceConnection, BSTR DestConnection);

Signature

Erik Ejlskov Jensen, Mobile App Dev MCTS
Check out my SQL Compact blog at
http://erikej.blogspot.com

> Erik:
> Thank you for your responding. I got a truble that we dont using
[quoted text clipped - 61 lines]
>>
>> - Show quoted text -

Reply to this Message