February 22, 2010

Vertica 4.0

Vertica briefed me last month on its forthcoming Vertica 4.0 release. I think it’s fair to say that Vertica 4.0 is mainly a cleanup/catchup release, washing away some of the tradeoffs Vertica had previously made in support of its innovative DBMS architecture.

For starters, there’s a lot of new analytic functionality. This isn’t Aster/Netezza-style ambitious. Rather, there’s a lot more SQL-99 functionality, plus some time series extensions of the sort that financial services firms – an important market for Vertica – need and love. Vertica did suggest a couple of these time series extensions are innovative, but I haven’t yet gotten detail about those.

Perhaps even more important, Vertica is cleaning up a lot of its previous SQL optimization and execution weirdnesses. In no particular order, I was told:

*Company V = one of the more prominent vertical-market application providers.

In other Vertica highlights:


12 Responses to “Vertica 4.0”

  1. Aster Data nCluster 4.5 | DBMS2 -- DataBase Management System Services on February 22nd, 2010 4:20 am

    […] Vertica, Netezza, and Teradata, Aster is using this week to pre-announce a forthcoming product release, […]

  2. David Aldridge on March 10th, 2010 4:34 am

    Heh, I always enjoy new release feature sets.

    Question: Why are are databases like soap powder? Answer: Because they’re all perfect until a new version comes out, and the company then tells you how limited their previous product was.

    “Now removes even baked on stains in a cold wash!”, “No need to pre-soak!” etc.. Or in this case “30-100X faster for large deletes!”

    Well, that’s marketing for you. They all play the same game.

  3. jiri on May 20th, 2010 2:02 pm

    I was on vertica presentation and vertica rep started comparing their SQL99 with PLSQL and T-SQL which to me is a bit strange and inaccurate. SQL has not much to do with PLSQL or T-SQL (some syntax is the same, but for example ORACLE SQL and PLSQL are two separate engines and truly serve two different purposes).

    Does this mean that vertica has no procedural language and thus has no stored procedures and triggers?

  4. Dave Menninger on May 24th, 2010 1:52 pm

    In reference to jiri’s comment above, the question asking for the comparison came directly from an attendee of the webinar. Perhaps we should have been more conscious of the procedural distinction in our response, but we interpreted the question as asking whether Vertica supports Oracle and Microsoft extensions to SQL. In response to jiri’s question, Vertica does not support stored procedures/triggers but does supports external procedures using industry standard languages such as Java, C, etc.

  5. Mike Stonebraker on “real column stores” | DBMS 2 : DataBase Management System Services on January 13th, 2011 3:54 am

    […] claims to have fixed a prior drawback to the feature — administrative complexity — in Vertica 4.0, I don’t have hard facts as to how complete the fix really […]

  6. Vertica projections — a lengthy overview | DBMS 2 : DataBase Management System Services on September 7th, 2011 10:09 pm

    […] on your logical schema. Note: Vertica has been claiming good support for all logical schemas since Vertica 4.0 came out in early […]

  7. Rajasekhar on January 23rd, 2012 1:02 pm


    Im using vertica 4.1 version.
    Yet i am unable to write a stored procedures, instead it supports External Procedures.
    Facing much trouble with this external procedures.
    Can anybody guide me , how to proceed with External Procedures.

    Thanks in advance.

  8. Navin Chakraborty on February 1st, 2012 6:40 am

    Hi Rajasekhar,

    First of all Vertica does not support Stored Procedure like other databases, the only way to incorporate an external procedure is to write a complete unix shell script and run the same via vsql, This is the only way to deploy your External Procedures. Maybe this will help you

  9. Amaresh Narayanan on October 10th, 2012 8:01 am

    We are migrating T-SQL to Vertica. Since we don’t stored procedure option in Vertica, we need to convert all T-SQL stored procedure to Vertica’s external procedure. Can you please help me on this?


  10. Pitfalls for Pollyannas | Strategic Messaging on December 4th, 2014 7:32 pm

    […] Overestimating the prevalence of specific use cases. In a classic example, Mike Stonebraker and others on the early Vertica team seemed convinced that — 20 years of contrary industry experience notwithstanding — most analytic RDBMS users would be content with star schemas. They were wrong. […]

  11. Introduction to Cloudera Kudu | DBMS 2 : DataBase Management System Services on September 28th, 2015 3:50 am

    […] Inserts arrive into something called a MemRowSet and are soon flushed to something called a DiskRowSet. Much as in Vertica: […]

  12. Cloudera Kudu deep dive | DBMS 2 : DataBase Management System Services on September 28th, 2015 3:53 am

    […] periodically flushed to the column store on disk. Queries are federated between these two stores. Vertica taught us to call these the WOS (Write-Optimized Store) and ROS (Read-Optimized Store) […]

Leave a Reply

Feed: DBMS (database management system), DW (data warehousing), BI (business intelligence), and analytics technology Subscribe to the Monash Research feed via RSS or email:


Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.