Newbie seeks advice on choice of database...

From: Vikas (vetaal_at_aol.com)
Date: 08/12/04

  • Next message: Lee Fesperman: "Re: What about a new DB without SQL?"
    Date: 11 Aug 2004 16:58:15 -0700
    
    

    Hi. I'm a .NET VB programmer realizing the error of my ways, and just
    turning to Java. I need to find a database that I can embed in my
    applications. The apps will run on desktops and on PDAs (perhaps
    later on some other mobile devices).

    So, what I need is:

      - A database that will run under Windows and (perhaps in a
    different, stripped-down version) on PDAs, particularly Pocket PCs.

     - That will allow for easy two-way synchronization of records between
    the destop installation and a PDA. Synchronization between multiple
    installations would be nice, but is not absolutely necessary.

     - If a third-party component or library could be embedded to handle
    the synchronization, that would be fine as well. But in any case,
    this kind of data exchange is essential, and I'd prefer not to have to
    try to code it myself.

    Number of records will be in the low thousands, perhaps with a maximum
    of seven thousand or so. Transactions and triggers would be great,
    but I can live without them.

    Price is a consideration; obviously cheap is good, and free is best,
    but if there was a great database engine out there that fits all my
    needs, I'd pay for it.

    Thanks for your help.

      -- Vikas


  • Next message: Lee Fesperman: "Re: What about a new DB without SQL?"

    Relevant Pages

    • Re: Error 25081: Incorrectly generating identities after a merge
      ... I started using the profiler to examine the synchronization. ... Creating a new database: ... > You should not need to compact the database after every synchronization. ...
      (microsoft.public.sqlserver.ce)
    • Re: multi-core ramifications w.r.t the monolithic linux kernel
      ... the data, you still need some form of synchronization, be it conventional ... memory access is the predominate performance factor vs. an OLTP database ... OLTP performance (well, it can increase response latency to remote clients, but only by a constant that has nothing to do with aggregate throughput). ... collections were unrefactorable into lock-free collections. ...
      (comp.arch)
    • Re: Why refactoring is better
      ... >Dont change the database structure at all. ... >Change structure on the fly, ... >even harder to write and test synchronization procedures. ... >imperative to never stop the database, and each has some cost. ...
      (comp.object)
    • Re: Cross linked Outlook databases on SBS server
      ... "Their outlook pst database is being sychronized with the server ... in another users database during the synchronization as they log off." ... Is the server here SBS 2003 Server? ...
      (microsoft.public.windows.server.sbs)
    • Re: Why refactoring is better
      ... Dont change the database structure at all. ... Change structure on the fly, ... even harder to write and test synchronization procedures. ... imperative to never stop the database, and each has some cost. ...
      (comp.object)