Get More Support

Here for you 24/7

learn more
VOD Free SDK

Start Building your Engine Now

Download Now
VOD Extranet

Access to patches, license management,
tech docs and more for existing VOD customers.

Learn More
Embedded DB4O (LINQ) vs Web Eloquera (SQL)
Last Post 17 Sep 2009 07:16 PM by RobertMcCarter. 3 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
dmytro
New Member
New Member
Posts: 1


--
20 Nov 2008 05:19 AM

    I am looking for a database to be used in a set of small to medium ASP.NET projects (using C#)

    I found two DBs that could help me with this.

    One is feature rich DB4O

    Advantages:

    - Lots of features

    - Supports LINQ that is easy to refactor

    - On a market for a long time 

    - Reasonably fast on small DB sizes 

    Disadvantages:

    - DB4O is targeting embedded market

    - Thread safe but single-user

    - I have had problems to make LINQ use indexes (perhaps I shall try latest development version) 

     

    Eloquera (SQL, eloquera.com)

    Advantages:

    - Supports powerful SQL like queries, looks like have query optimizer that uses indexes in efficient way

    - Supports property indexing 

    - Designed for Web, multiuser

    - It's fast, really fast.

    - Supports really big DB sizes 

    Disadvantages:

     - I never seen them before on the market, looks like new guys

    - Support for complex field types looks like in progress.

    - Transactions also in progress 

     

    I looked into FastObject and Objectivity - they are expensive (FastObjects in a range of 40K euro) and slow in .NET environment.

    I am very happy to use db4o, the only concerns about LINQ indexing and lack of multiuser support

    Is there any work in this direction going? 

    Carl Rosenberger
    Veteran Member
    Veteran Member
    Posts: 2173


    --
    20 Nov 2008 01:22 PM
    db4o optimizes LINQ queries where the analyzer
    understands them well enough. The very first
    query against an assembly may be a bit slower
    than later ones, because the assembly must be
    analyzed once completely.

    db4o also provides multiuser support.
    Please read Chapter 11 "Client/Server" in the
    db4o tutorial.
    RobertMcCarter
    New Member
    New Member
    Posts: 8


    --
    17 Sep 2009 07:14 PM

    According to http://developer.db4o.com/forums/th...51714.aspx db4o is a database-level-lock product that is designed for embedded.  It doesn't scale very well on the server side of things.

    I have done a number of performance tests of Eloquera and it is twice as fast than my traditional ORM solution against SQL Server, and it scales linearly whereas my ORM/SQLServer solution scales exponentially (yikes).

    I'd go with Eloquera (and I don't work there or have any stock :-)

    RobertMcCarter
    New Member
    New Member
    Posts: 8


    --
    17 Sep 2009 07:16 PM
    That said, for my embedded WPF application I'm using DB4O because of the excellent LINQ support.
    You are not authorized to post a reply.


    Active Forums 4.3