Re: Data storage solution advice sought...

From: Ginny Caughey [MVP] (ginny.caughey.online_at_wasteworks.com)
Date: 09/22/04 

Date: Wed, 22 Sep 2004 13:59:52 -0400

Neil,

I'll just make a couple of comments:

First, forget XML. It will be too bulky and too slow for the data volumes
you're anticipating.

Second, although SqlMobile 2005 will offer many nice enhancements, until a
release schedule has been announced, it's probably not a good idea to plan
around that. Also be aware that some legacy hardware won't support Compact
Framework version 2 anyway.

That mostly leaves SqlCe2, but that's really not a bad choice. The database
is a single file on the device, so you could offer a backup strategy for
that file. You do have the limitation that the database is single user of
course (until Sql Mobile.) 

-- 
Ginny Caughey
.Net Compact Framework MVP
"Neil Kiser" <neil@NOSPAMkiserville.com> wrote in message 
news:50419532-BCFB-451A-9103-905FC0654A52@microsoft.com...
> Ok, here's my scenario:
> -I am creating an application that will work with data extensively
> -The data storage solution will come pre-populated with a large amount of
> data from me, (about 1 or 2 MB's worth)
> -the user is free to modify, and add data.  In fact the 'adding of data' 
> is
> expected.  I would expect the big users to add 1 to 5 more megabytes worth 
> of
> data, although I don't want to place any real limit on the user.  I could 
> see
> someone with a storage card wth a 100MB db if they store images in the
> database, as it will allow.
> -Replicating with a SQL Server will not be offered as an option as this is
> for consumer, not commercial use.
> -the ability to back-up the db will be required in some form (xml dump, 
> copy
> db file to host machine, etc...)
> - I have considered, but have not committed to, developing a desktop 
> version
> of teh app for easier input.  I am loathe to do this however and, as such,
> rate the possibility as low.
> -the data stored in the database is relational
> - I would like to password protect and encrypt the database.  I don't want
> anyone using the data I am going to seed the database with.
>
> I see several options:  SQl Server CE 2.0 (which is what I am using now in
> my development), XML files, Pocket Access, SQL Server 2005 Mobile.
>
> SQL Server CE 2.0:  PROS: fastest solution? I'm comfortable with it.
> Database can be locked down and encrypted.  relational database.  CONS: my
> main concern is the size of the DB dlls, the fact that only one database 
> can
> be opened at a time, and the lack of a clear backup strategy since my
> customers will not have SQL server desktop version to replicate to :)
>
> XML Files:  PROS:  no storage overhead.  CONS: just seems messy.  In
> addition, I have to deal with image storage and relational data.  Just
> doesn't seem right to me to use XML files in this case.
>
> Pocket Access - PROS:  I understand that I can use ActiveSync wupport to
> backup the database.  Can I merge a desktop Access database with the 
> Pocket
> Access data?  CONS: No CF support.  I just can't seem to find much about
> Pocket Access.  I find articles on how to access data - but how is the
> database created in the first place?  How do I construct a Pocket Access 
> DB?
> I have a schema already created in SQL Server and I have data already 
> stored
> in it.  How do I get this schema and data into a Pocket Access DB?
>
> SQL Server 2005 Mobile - PROs:  ?  CONS:  still in beta (but should be out
> by the time I am ready to release).  Doesn't seem to solve many of the
> problems I have with SQL Server CE 2.0.  It does, however, allow more than
> one connection to the DB at a time - at least, so I have been told.
>
> My question, after all of that, is so I have my facts straight?  and what
> would others recommend?
>
> BTW, I am not that concerned over the SQL Server CE overhead.  I reckon 
> that
> anyone who will purchase my program will have no problem acquiring a 
> storage
> card upon which to place their data (I know that this doesn't directly
> address the sql dlls).  I just think that in the end, it will all even 
> out...
> for the market segment that would be interested in my product.  So I'm
> thinking that this "con" probably isn't a deal-breaker for me.  I'm more
> concerned about what data backup solution I will be able to provide my 
> users,
> especially if they are storing their db file on a storage card and not in
> their 'My Documents' folder.
>
> Thanks,
> -Neil K.

Relevant Pages

  • Data storage solution advice sought...
    ... someone with a storage card wth a 100MB db if they store images in the ... database, as it will allow. ... -Replicating with a SQL Server will not be offered as an option as this is ... Pocket Access - PROS: I understand that I can use ActiveSync wupport to ...
    (microsoft.public.dotnet.framework.compactframework)
  • RE: Data storage solution advice sought...
    ... Data storage solution advice sought... ... > database, as it will allow. ... > my development), XML files, Pocket Access, SQL Server 2005 Mobile. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: ASP SITE with SQL Server--best way to backup?
    ... Have them restore the backup made 4 days ago. ... <<<how hard would it be to restore from XML to the database if things went ... meaning that you could restore the data easily, but only if the SQL Server ... XML per se. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ASP SITE with SQL Server--best way to backup?
    ... Have them restore the backup made 4 days ago. ... <<<how hard would it be to restore from XML to the database if things went ... meaning that you could restore the data easily, but only if the SQL Server ... XML per se. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Recommendations - XML or traditional relational structure
    ... As one who has designed database systems and transport mechanisms for the ... public health community I would ... HL7 ver 3 is built on XML and RIM. ... The backend is SQL Server 2005. ...
    (microsoft.public.sqlserver.xml)
Loading