Hi, Right, but in the case when you take the data 30 minutes, you take all the data, and the bank have to see what should be changed or inserted? is not better you take only the new data in this way will always be inserted? I do it today Att, On 16/04/2015 10:47, users-list-request@monetdb.org wrote:

Send users-list mailing list submissions to users-list@monetdb.org

To subscribe or unsubscribe via the World Wide Web, visit https://www.monetdb.org/mailman/listinfo/users-list or, via email, send a message with subject or body 'help' to users-list-request@monetdb.org

You can reach the person managing the list at users-list-owner@monetdb.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of users-list digest..."

Today's Topics:

1. Re: MonetDB vs Vertica CE (shamsul hassan)

----------------------------------------------------------------------

Message: 1 Date: Thu, 16 Apr 2015 14:47:46 +0100 From: shamsul hassan <shamsulbuddy@gmail.com> To: Communication channel for MonetDB users <users-list@monetdb.org> Subject: Re: MonetDB vs Vertica CE Message-ID: <CAONo-du24VrQ_PR4nzNq7rT7Uw47fKQb5Pr376UWEDmTbCN7qQ@mail.gmail.com> Content-Type: text/plain; charset="utf-8"

there is only one thing which has stopped me for using MonetDB in production is the lack of UPSERT operation. In my case new data comes every 30 mins and I cannot truncate and load the whole table again. Ideally an UPSERT would have helped here as it will only touch those records which are new or changed without truncating the whole table.

I raised the question few days before in Community list but didn't get any useful answer.

If i get any workaround for these UPSERTS the i would be as happy as pig in dirty water :)

Thanks

On Thu, Apr 16, 2015 at 2:37 PM, Ruben Silva < ruben.silva@cortex-intelligence.com> wrote:

...

Hello Luciano,

I don't have a full grasp of the new stuff introduced into MonetDB in the last year, but as far as I know there are still major differences between the two systems for me the most important is scalability. Vertica has no single point of failure when working as a cluster. However the CE version is limited to three nodes, so scalability is also limited in that case.

Vertica relies heavily on projections as a way to improve performance. If your data model is relatively stable it is something fairly easy to use, but if your data model changes at a high rate you will have a considerable amount of additional work managing the projections. Also if you use many projections they will hurt your DML statements performance.

MonetDB feeds on CPU and has no boundaries for its appetite, consuming as much resources as possible in order to respond to a single statement. That can be very good or very bad, it depends on your use case. Vertica has resource pools that are used to regulate the stuff (IO, Ram, CPU) that each query is allowed to use.

I don't know your use case (and that is crucial for a good advice), but if you are considering a scenario where you have a single machine for the database system, then go with MonetDB without any doubt. It is just faster and simpler.

Cumprimentos (Regards),

2015-04-16 14:04 GMT+01:00 Luciano Sasso <luciano@gsgroup.com.br>:

...

Hi,

The team of staff this questioning me about using Vertica, but it has limitations on the CE version. Someone already used the Vertica has some advantage over MonetDB?

-- Luciano Sasso Vieira Data Scientist & Solutions Architect

luciano@gsgroup.com.br <http://www.gsgroup.com.br> | tel: 17 3353-0833 | cel: 17 99706-9335 www.gsgroup.com.br

------------------------------ [image: Avast logo] <http://www.avast.com/>

Este email foi escaneado pelo Avast antiv?rus. www.avast.com

_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list