[xquery-talk] Finding a XML-Database to fit our needs
sterini at gmail.com
Sat Dec 15 12:34:18 PST 2007
> Concurrent inserts and updates.
The only native database that allows node level locking granularity
that is required for concurrent updates, is RainingData's TigerLogic.
Other databases handle concurrency on the collection level, though
you'd have to chunk and manage this chunked data at the locking
granularity you'd like to achieve. TigerLogic implicitly locks at the
most granular level and has XQuery extensions to allow explicit
specification of locks.
On Dec 15, 2007 10:30 AM, Johan Mörén <johan.moren at gmail.com> wrote:
> Hi all,
> I'm new to the list and work for a company in Stockholm, Sweden.
> We are currently evaluating a move from storing our data in a RDMBS (Oracle
> 10g) to storing it as native XML. The reason for doing this is that all
> communication to the persistence layer is done via SOAP and we believe we
> can save a lot of effort and time if we persist our data in the same format
> as we communicate it to the outside world.
> We are looking for a solution that can handle approximately 16 000 000
> documents ranging from 50 to 200 KB in size. About 5k to 20k documents will
> be updated daily. The documents are all derived from the same base type and
> are described by a common schema. There are 5 sub-types that could be split
> into different collections where the largest, in terms of number of
> documents, would be about 8-9 million in size.
> Practically all documents have relationships described to documents
> belonging both to their own type but also to the other types so navigation
> of these relationships must be possible for querying purposes.
> The documents are very data centric, containing very little free text. But
> some fields will need to be backed by a free-text-index for querying. Since
> operators will work online with the data, query times will need to be
> reasonably fast for not to complex queries.
> Apart from the above. The database should support:
> * Concurrent inserts and updates.
> * XQuery 1.0 support.
> * Any fragmentation of the documents (to handle the size) should be
> transparently handled by the database.
> * Both commercial and open source alternatives are of interest.
> Any input, experiences and pointers on where to look would be very much
> "You can't always write a chord ugly enough to say what you want to say,
> so sometimes you have to rely on a giraffe filled with whipped cream." -
> Frank Zappa
> talk at x-query.com
More information about the talk