October 18, 2011

Vertica Community Edition

The press release announcing Vertica’s Community Edition is a bit vague. And indeed, much of what I know about Vertica Community Edition is along the lines of “This is what I think will happen, but of course it could still change.” That said, I believe:

I’m a big supporter of the Vertica Community Edition idea, for four reasons:


7 Responses to “Vertica Community Edition”

  1. Commercial software for academic use | DBMS 2 : DataBase Management System Services on October 18th, 2011 10:49 am

    […] You can put >1 petabyte into [name redacted],* among others; [name redacted]* should be out soon with a generously free offering for academic users. Edit: That would be Vertica. […]

  2. Colin Mahony on October 18th, 2011 5:04 pm

    Regarding your bullet:

    “HP Vertica would be annoyed if you stuck a free copy of Vertica on each of 50 nodes and managed the whole thing via, say, Hadapt.”

    This would violate the CE license agreement as we do not allow this type of sharding multiple CE databases together through any app tier…

    Similar to the point above, multiple CE editions connected for DR is not permitted in the CE version- customers would need the enterprise edition for this. A separate copy for development is permitted.

  3. Mohan on November 10th, 2011 10:31 pm

    I am a tad confused, within the limits of < 1 terabytes and <= 3 nodes, can the CE edition be used in production/commercial context ?

  4. Curt Monash on November 10th, 2011 11:28 pm

    Yes, if you’re willing to live with what the 3 node limitation implies for disaster recovery and so on.

  5. DBguy on January 16th, 2012 10:32 am

    So where is it? It’s been almost 3 month since it was announced.

  6. DBguy on January 24th, 2012 3:36 pm

    And what is data size (that’s limited to 1TB):
    – uncompressed size of all projections
    – compressed size of all projections
    – uncompressed size of all super projections
    – total disk usage by Vertica
    – something else?

  7. Vovaka on March 21st, 2012 8:46 am

    The data sampled for the estimate is treated as if it had been exported from the database in text format (such as printed from vsql). This means that Vertica evaluates the data type footprint sizes as follows:

    vsql is a character-based, interactive, front-end utility that lets you type SQL statements and see the results. It also provides a number of meta-commands and various shell-like features that facilitate writing scripts and automating a variety of tasks.

    •Strings and binary types (CHAR, VARCHAR, BINARY, VARBINARY) are counted as their actual size in bytes using UTF-8 encoding.
    •Numeric data types are counted as if they had been printed. Each digit counts as a byte, as does any decimal point, sign, or scientific notation. For example, -123.456 counts as eight bytes (six digits plus the decimal point and minus sign).
    •Date/time data types are counted as if they had been converted to text, including any hyphens or other separators. For example, a timestamp column containing the value for noon on July 4th, 2011 would be 19 bytes. As text, vsql would print the value as 2011-07-04 12:00:00, which is 19 characters, including the space between the date and the time.
    NOTE: Each column has an additional byte for the column delimiter.

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.