vertica - Developer IT

How do I do a Crosstab in Vertica

- by Russ Bradberry

What is the Vertica equivalent of crosstab or pivot table found in PostgreSQL and other RDBMS's?

Using an ODBC application with a JDBC driver

My company uses Vertica. We have Python applications that connect to it with pyodbc. I do most of my development on a Mac (Snow Leopard) and unfortunately Vertica has not released ODBC drivers for Mac. They do have JDBC drivers though. I don't think developing in Jython is a good compromise. Is there any way to use JDBC drivers with an ODBC application? Some kind of ODBC connector?

Read the article

How do I Put Several Select Statements into Different Columns

- by Russ Bradberry

I basically have 7 select statement that I need to have the results output into separate columns. Normally I would use a crosstab for this but I need a fast efficient way to go about this as there are over 7 billion rows in the table. I am using the vertica database system. Below is an example of my statements: SELECT COUNT(user_id) AS '1' FROM event_log_facts WHERE date_dim_id=20100101 SELECT COUNT(user_id) AS '2' FROM event_log_facts WHERE date_dim_id=20100102 SELECT COUNT(user_id) AS '3' FROM event_log_facts WHERE date_dim_id=20100103 SELECT COUNT(user_id) AS '4' FROM event_log_facts WHERE date_dim_id=20100104 SELECT COUNT(user_id) AS '5' FROM event_log_facts WHERE date_dim_id=20100105 SELECT COUNT(user_id) AS '6' FROM event_log_facts WHERE date_dim_id=20100106 SELECT COUNT(user_id) AS '7' FROM event_log_facts WHERE date_dim_id=20100107

Read the article

What's the difference been NoSQL and a Column-Oriented database?

- by Tedk

The more I read about NoSQL, the more it begins to sound like a column oriented database to me. What's the difference between NoSQL (e.g. CouchDB, Cassandra, MongoDB) and a column oriented database (e.g. Vertica, MonetDB)?

Read the article

Don’t Forget! In-Memory Databases are Hot

- by andrewbrust

If you’re left scratching your head over SAP’s intention to acquire Sybase for almost $6 million, you’re not alone. Despite Sybase’s 1990s reign as the supreme database standard in certain sectors (including Wall Street), the company’s flagship product has certainly fallen from grace. Why would SAP pay a greater than 50% premium over Sybase’s closing price on the day of the announcement just to acquire a relational database which is firmly stuck in maintenance mode? Well there’s more to Sybase than the relational database product. Take, for example, its mobile application platform. It hit Gartner’s “Leaders’ Quadrant” in January of last year, and SAP needs a good mobile play. Beyond the platform itself, Sybase has a slew of mobile services; click this link to look them over. There’s a second major asset that Sybase has though, and I wonder if it figured prominently into SAP’s bid: Sybase IQ. Sybase IQ is a columnar database. Columnar databases place values from a given database column contiguously, unlike conventional relational databases, which store all of a row’s data in close proximity. Storing column values together works well in aggregation reporting scenarios, because the figures to be aggregated can be scanned in one efficient step. It also makes for high rates of compression because values from a single column tend to be close to each other in magnitude and may contain long sequences of repeating values. Highly compressible databases use much less disk storage and can be largely or wholly loaded into memory, resulting in lighting fast query performance. For an ERP company like SAP, with its own legacy BI platform (SAP BW) and the entire range of Business Objects and Crystal Reports BI products (which it acquired in 2007) query performance is extremely important. And it’s a competitive necessity too. QlikTech has built an entire company on a columnar, in-memory BI product (QlikView). So too has startup company Vertica. IBM’s TM1 product has been doing in-memory OLAP for years. And guess who else has the in-memory religion? Microsoft does, in the form of its new PowerPivot product. I expect the technology in PowerPivot to become strategic to the full-blown SQL Server Analysis Services product and the entire Microsoft BI stack. I sure don’t blame SAP for jumping on the in-memory bandwagon, if indeed the Sybase acquisition is, at least in part, motivated by that. It will be interesting to watch and see what SAP does with Sybase’s product line-up (assuming the acquisition closes), including the core database, the mobile platform, IQ, and even tools like PowerBuilder. It is also fascinating to watch columnar’s encroachment on relational. Perhaps this acquisition will be columnar’s tipping point and people will no longer see it as a fad. Are you listening Larry Ellison?

Developer IT