Re: SQL CE 3 and CF 1.0 support

From: Ginny Caughey [MVP] (ginny.caughey.online_at_wasteworks.com)
Date: 02/14/05


Date: Mon, 14 Feb 2005 07:58:34 -0500

Strider,

Ok thanks fot the explanation. I guess when you decide you're ready for
CFv2, then you'll move to SqlCe3. I don't see any other way to do it, and
you'd have to change the underlying app if you moved to a 3rd party data
storage solution anyway.

-- 
Ginny Caughey
.Net Compact Framework MVP
"Strider" <Strider@discussions.microsoft.com> wrote in message 
news:EDF202D7-EEBD-49B3-A540-7870E4A93D6B@microsoft.com...
> The problem is not the device but the deployment itself.
>
> We have designed our application so that all data access logic is
> abstracted behind Microsoft's Sytem.Data interfaces. All data access
> objects are created using factory methods.
>
> So, there is no real dependency on SQL CE. We could rollout the new engine
> using our automated upgrade mechanism and at the same time upgrade the
> database file to version 3, without the end user noticing a thing (except
> from the engine download and the database upgrade delay).
>
> Now Microsoft tells me I need to purchase Visual Studio 2005, rebuild my
> application on CF 2.0, and install CF 2.0 on all the devices.
>
> I don't want Microsoft to tell me when to upgrade to VS 2005 or .NET
> Framework 2.0. These are decisions that I need to make for myself. What I
> need from Microsoft is to provide me with a descent database engine that
> doesn't blow
> on my user's face every week!
>
> And I don't want to hear of storage cards being the root of all evil 
> again.
> I know of applications that have been using flat files on storage cards 
> for
> storing data and have never had a single corruption problem for years!
> I also know of applications that have been using SQL CE databases in RAM 
> and
> still experience corruption problems. All these are competitive 
> applications
> that I haven't developed myself (in case you think that I am a very bad
> developer who doesn't have a clue on how to write data access code :-) ).
>
> Thanks for listening Ginny!
>
> "Ginny Caughey [MVP]" wrote:
>
>> Strider,
>>
>> My understanding is that Sql CE 3 *requires* .NetCFv2 for itself. So 
>> there
>> really wouldn't be any way to run it on a device that can't run .NetCFv2.
>>
>> SQL Mobile (SqlCE3) is certainly a big improvement over SqlCE2, so I
>> understand your frustation. What device do you want to target that won't 
>> be
>> capable of running .NetCFv2?
>>
>> -- 
>> Ginny Caughey
>> ..Net Compact Framework MVP
>>
>>
>> "Strider" <Strider@discussions.microsoft.com> wrote in message
>> news:B2449FBF-AE19-493D-A8EA-9CD6FC9A1733@microsoft.com...
>> > Makes sense! Sql CE 2 was such a "robust" engine that
>> > noone should need to upgrade right?
>> >
>> > Well, If I had any doubts about dropping SQL CE
>> > (in hope that version 3 would present a descent database engine)
>> > they're all gone now!
>> >
>> > Does Microsoft consider CF 1.0 applications as legacy ones?
>> > Or is it such a great challenge to write a provider for CE 3 on CF 1.0?
>> > Is it just another "motive" to port all mobile apps to CF 2?
>> >
>> > For me, the answer to all these questions is moving to a third party
>> > database engine - possibly Sybase Ultralite.
>> >
>> > (Porting all my apps to Java be the next step???)
>> >
>> > http://www.msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.dotnet.framework.compactframework&mid=f59136de-5c19-42b1-b27f-591a367b0826&sloc=en-us
>> >
>> >
>> >
>> > "Ginny Caughey [MVP]" wrote:
>> >
>> >> SQL Mobile (aka SQL 3) requires Compact Framework v2. With .NetCF v1 
>> >> you
>> >> should use Sql CE 2.
>> >>
>> >> -- 
>> >> Ginny Caughey
>> >> ..Net Compact Framework MVP
>> >>
>> >>
>> >> "Strider" <Strider@discussions.microsoft.com> wrote in message
>> >> news:5B8DB8C7-4812-4EB1-B67B-607DF861406B@microsoft.com...
>> >> > Does anybody know anything about SQL CE 3 support for the
>> >> > 1.0 version of the Compact Framework?
>> >>
>> >>
>> >>
>>
>>
>> 


Relevant Pages

  • Re: Subject:Writing a db independent data access layer with DAAB:How?
    ... > was researching how i can write a database independent data access layer. ... > be able to work both in SQL and Oracle. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Database owner after SQL 2005 upgrade
    ... I don't believe this is new behavior with SQL Server 2005. ... upgrade a SQL Server 7 database to SQL Server 2000, ... database in the compatibility mode that matches the product version it came ...
    (microsoft.public.sqlserver.setup)
  • Re: Desperate - WSS2.0 upgrade to WSS 3.0 trashed DB no either won
    ... You could install SQL 2005 Studio Management Express and attach the database from your SQL environment. ... to upgrade the database, but as I have stated earlier, I can't upgrade using ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... MSDE to store SharePoint uses the MSSQL$SharePoint database, ... SharePoint named instance to full SQL. ... You cannot upgrade the Monitoring instance to SQL ... What I see is the SQL server group and under ...
    (microsoft.public.windows.server.sbs)
  • Thanks Hari [n/t]
    ... Yes SQL 6.5 databases wil be safe. ... The upgrade wizard ... >> I need to do an upgrade of an SQL 6.5 database to SQL ...
    (microsoft.public.sqlserver.server)

Loading