Welcome to the New Vertica Blog!

Posted March 28, 2019 by Ben Smith, Senior Product Marketing Manager

Announcing Vertica Version 9.2.1 – Take Analytics Efficiency to the Next Level

Paige Roberts, Vertica Open Source Relations Manager
May 10, 2019

This week, some very cool things have gone into the newest version of the that make your analytics fly and save on your AWS budget. The theme for this release is Improving Vertica in Eon Mode Integration with Amazon S3, and there are a whole bunch of new features designed to do exactly that. But,...

Chicago cityscape with various data type icons and network connection concept

Can You Hear Me Now? Network Optimization at Work

Jeff Healey, Sr Director, Vertica Product Marketing at Micro Focus
May 1, 2019

For sports fans, there’s nothing that matches the heart-stopping action of the NCAA Division I Men’s Basketball Tournament – more commonly known as March Madness. This year’s tournament delivered a four-year high in terms of its , causing an advertiser frenzy in hopes to capture those audiences. If you watched this year’s tournament, you couldn’t...

Close All Sessions for a User with a Single Command

Jim Knicely, Big Data Solutions Architect, Vertica
May 9, 2019

The Vertica CLOSE_SESSION function can be used to close a user session one session at a time. If you have a user that has opened a bunch of sessions, closing them one at a time would be a very long and tedious process. That’s where the CLOSE_USER_SESSIONS function comes in handy. It will stop all...

Vintage businessman concept wearing futuristic helmet at office

Table Schemas for Global and Local Temp Tables

Jim Knicely, Big Data Solutions Architect, Vertica
May 8, 2019

By default, Vertica stores Global Temporary Tables in the Public schema and Local Temporary Tables in the V_TEMP_SCHEMA schema. Vertica uses the default schemas if a schema name is not provided when creating temporary tables: I can specify a different schema name for a Global Temporary Table: But not for a Local Temporary Table: Helpful...

DATAx Gaming Analytics Summit in San Francisco

Ben Smith, Senior Product Marketing Manager
May 8, 2019

According to a recent from Newzoo and Arm, the Mobile Gaming market is expected to top $100 billion by 2021, up from $56 billion in 2017. As the global adoption of smartphones continues to expand, so too does the use of mobile and online gaming. To capitalize on this growth, game developers are looking for...

Subscribe For Email Updates

Enter your email address to receive the monthly Vertica newsletter.

Make Comparisons on Subqueries that Return Multiple Rows

Jim Knicely, Big Data Solutions Architect, Vertica
May 7, 2019

You typically use comparison operators (such as =, >, < ) only on subqueries that return one row. With ANY and ALL operators, you can make comparisons on subqueries that return multiple rows. I want to check if an integer is greater than any of the integers in a set of rows. If I try...

Create a Python UDx to Order a List of Values

Jim Knicely, Big Data Solutions Architect, Vertica
April 25, 2019

User-Defined Extensions (UDxs) are functions contained in external shared libraries that are developed in C++, Python, Java, or R using the Vertica SDK. The external libraries are defined in the Vertica catalog using the CREATE LIBRARY statement. They are best suited for analytic operations that are difficult to perform in SQL, or need to be...

See You at IoT World Conference Next Month

Ben Smith, Senior Product Marketing Manager
April 25, 2019

Are you attending the IoT World Conference in Santa Clara from May 13-16th? Come by booth #1254 to hear why more and more companies, including medical device manufacturers, wearable product developers, network service providers, and manufacturing intelligence software companies, are turning to Vertica to manage their growing volumes of IoT data. Vertica is purpose-built for...

Explore Popular Topics

DBadmin
SQL
Best Practices
machine learning
Advanced Analytics
VSQL
Cloud
AWS
Eon Mode
Checklists
Security
Time series
Vertica 9
Vertica
Projections

Forcing a Merge Join

Jim Knicely, Big Data Solutions Architect, Vertica
April 23, 2019

The Vertica optimizer implements a join with one of the following algorithms: Merge join is used when projections of the joined tables are sorted on the join columns. Merge joins are faster and use less memory than hash joins. Hash join is used when projections of the joined tables are not already sorted on the...

Displaying the Vertica Code Name

Jim Knicely, Big Data Solutions Architect, Vertica
April 23, 2019

Every major release of Vertica has a code name. To find out the Vertica code name of your database, you can query the DC_STARTUPS Data Collector table. Example: Helpful Link: Have fun!

Machine learning robot studying equations and graphs

Doing In-Database Machine Learning 1 – Why Would You Do That?

Waqas Dhillon, Product Manager - Machine Learning, Vertica
April 22, 2019

Co-authored with Paige Roberts. A lot of modern like Vertica allow you to do machine learning from end to end, right in the database, rather than moving and transforming the data first into something like a Spark dataframe or a Python data structure. Whenever people hear about this capability, they have two questions. The first...

Vintage businessman concept pointing on the wall wearing futuristic helmet at office

Descending Sequences

Jim Knicely, Big Data Solutions Architect, Vertica
April 17, 2019

The default increment for a Vertica sequence is 1. But you can also create a sequence that has a negative increment so that you can have a count down. Example: Helpful Links: Have fun!

Display Session Sequence Cached Values Remaining

Jim Knicely, Big Data Solutions Architect, Vertica
April 17, 2019

To optimize the performance of large INSERT SELECT and COPY operations, Vertica uses sequence caching. To allocate cache among the nodes in a cluster for a given sequence, Vertica uses the following process: By default, when a session begins, the cluster initiator node requests cache for itself and other nodes in the cluster. The initiator...

Is This a Leap Year?

Jim Knicely, Big Data Solutions Architect, Vertica
April 16, 2019

A Common Year in the Gregorian calendar has 365 days. A Leap Year, which has 366 days, occurs nearly every 4 years. One algorithm to determine if a year is a Common or a Leap Year is: I’d like to create a user-defined SQL function in Vertica that will let me know if the year...