So you probably know that I have been working with HP’s Vertica. I’m very glad that I had this opportunity to interact with something like this. The technology behind it is pretty new and immature and lacks the power of PL/SQL but the speed that it achieves through massive parallel execution of queries is simply amazing. I don’t know if you have heard of the term K-Safe or K-Safety. When I first heard it, I had no idea what it was....
Hey there, I guess you have been having a lot fun with your Vertica databases. I thought I’d share some of the things that I did to improve my query performance. Tables and Projections in Vertica In Vertica even though we access data through tables everything is stored in projections which are stored among nodes in various ways depending on the K Safety and the Segmentation options that we choose when creating the table....
For the past few weeks I have been really depressed and pissed at work. I love what I am currently working on but unfortunately I just don’t have enough freedom to do what I want. How would you feel if you had to rely on silly things on a person who belonged to a completely different team? I work on Vertica. And Vertica has something called a Database designer, which for some reason can only be run by someone who has admin rights....
Vertica has a special feature to join tables and fill in the last available values where values would otherwise be null. I had a similar use case and wanted to test how I could make the best use of it. I played with simple examples and got it right, but with a slightly more complex one, I was stuck or maybe I just couldn’t understand what was happening. So I posted a question at Stackoverflow
I had a problem creating a table with just SQL that is supported by Vertica. Most of the solutions that I came across online were using procedures. But after a lot of playing around and reading vertica documentation I found a solution to my problem. read more about the problem and the solution at Stackoverflow