Sybase Analytics

Hi, I’m the product manager for Sybase IQ and Sybase ETL. Ever since the new Sybase ETL v4.8 was released in March this year, I have been bombarded with questions from customers, partners, and our sales engineers. So I decided to write some Blogs to share with more of you more rapidly. So here you go, the first Blog on Sybase ETL.

Majority of the questions fall into three categories: what is the new Sybase ETL? why Sybase is offering its own ETL tool? What are the key benefits of using the latest release of Sybase ETL

The first question sounds easy and here is the standard answer: Sybase ETL provides extract, transform, and load (ETL) capabilities for consolidating data into IQ from heterogeneous data sources. But there is certainly more to that. And the most important thing here is that the new Sybase ETL v4.8 only supports Sybase IQ as the target, hence we are able to optimize it to work best with Sybase IQ’s column-based architecture. I’ll cruise into the details on this in my next Blog.

Why Sybase is offering its own ETL tool? Our goal has always been to bring more values to Sybase IQ customers with a complete stack of technologies that are well integrated, fully optimized for Sybase IQ’s unique architecture, and comes with great ease of use. The Sybase ETL v4.8 is geared specifically for customers who are implementing small to medium IQ reporting server projects where quick time to value and great return of investment is essential under the current economic situation.

The new Sybase ETL v4.8 offers a number of benefits to our customers. In short, Sybase ETL v4.8 supports all the IQ bulk load interfaces and provides bulk mode Upsert and Delete capability that is specifically optimized for IQ to address the incremental load need. These capabilities, along with the fact that it is easy to develop and deploy, and is offered at an affordable price point, make Sybase ETL v4.8 very attractive to Sybase IQ report server users who need fast time to production, are faced with tough budget constraints, and are looking for a good alternative to developing custom-coded loading scripts.

This is all for my first Blog on Sybase ETL. My next one will dive into the details on how Sybase ETL is fully optimized for loading into Sybase IQ and how it meets the unique loading requirements of the column-based architecture. By the way, you can also find more information about Sybase ETL at http://www.sybase.com/files/Data_Sheets/SY_ETL_DS_20090615.pdf

Yiwen Huang