http://www.rittmanmead.com/2006/10/11/oracle-buy-sunopsis/ Delivered Intelligence Wed, 17 Mar 2010 13:47:41 -0400 http://wordpress.org/?v=2.8.4 hourly 1 http://www.rittmanmead.com/2006/10/11/oracle-buy-sunopsis/comment-page-1/#comment-1530 Mark Rittman » Getting Started with Sunopsis Data Conductor Fri, 19 Jan 2007 22:40:03 +0000 http://www.rittmanmead.com/wp2/2006/10/11/oracle-buy-sunopsis/#comment-1530 [...] Getting Started with Sunopsis Data Conductor If you were reading this blog a month or so ago, you may well have seen a posting about Oracle’s purchase of Sunopsis. Sunopsis are a French company with offices around the world that specializes in ETL tools; Oracle have bought them because they bring to Oracle the ability to load and transform data on all data platforms, not just the Oracle database, whilst keeping to the current OWB philosophy of using the database as the ETL engine, rather than using a separate ETL hub with it’s own language, database and so on. I met up with some of the Sunopsis team in the UK last week to go through their product architecture, and to get hold of an evaluation copy of Sunopsis Data Conductor, the main part of their wider ETL and data movement suite. I’ll be covering Data Conductor in the forthcoming Oracle Business Intelligence book I’m currently finalizing, and so I thought it worthwhile putting the product through it’s paces and seeing how it compares to Oracle Warehouse Builder. Data Conductor comes with an evaluation guide and dataset as part of the download, and so I’ve worked through this first, and I’ll move on to transforming and loading my own data later on. Taking a quick look at the product architecture first, like Warehouse Builder Sunopsis Data Conductor uses the target data warehouse, or in some circumstances the source database, to do the data transformation rather than using a separate ETL server. The rationale behind this is that set-based transformations on the target data warehouse are usually faster than row-by-row transformations and inserts performed by an ETL server, and by buying Sunopsis Data Conductor, you preserve and leverage the investment you’ve made in your database engine rather than paying all over again for a separate ETL box to do the work for you. Like Warehouse Builder, Data Conductor is based around a repository that can be held in any relational database. It stores metadata about the source and target databases, details of the mappings (called “Interfaces” in Data Conductor), the process flows and details of the execution results. [...] [...] Getting Started with Sunopsis Data Conductor If you were reading this blog a month or so ago, you may well have seen a posting about Oracle’s purchase of Sunopsis. Sunopsis are a French company with offices around the world that specializes in ETL tools; Oracle have bought them because they bring to Oracle the ability to load and transform data on all data platforms, not just the Oracle database, whilst keeping to the current OWB philosophy of using the database as the ETL engine, rather than using a separate ETL hub with it’s own language, database and so on. I met up with some of the Sunopsis team in the UK last week to go through their product architecture, and to get hold of an evaluation copy of Sunopsis Data Conductor, the main part of their wider ETL and data movement suite. I’ll be covering Data Conductor in the forthcoming Oracle Business Intelligence book I’m currently finalizing, and so I thought it worthwhile putting the product through it’s paces and seeing how it compares to Oracle Warehouse Builder. Data Conductor comes with an evaluation guide and dataset as part of the download, and so I’ve worked through this first, and I’ll move on to transforming and loading my own data later on. Taking a quick look at the product architecture first, like Warehouse Builder Sunopsis Data Conductor uses the target data warehouse, or in some circumstances the source database, to do the data transformation rather than using a separate ETL server. The rationale behind this is that set-based transformations on the target data warehouse are usually faster than row-by-row transformations and inserts performed by an ETL server, and by buying Sunopsis Data Conductor, you preserve and leverage the investment you’ve made in your database engine rather than paying all over again for a separate ETL box to do the work for you. Like Warehouse Builder, Data Conductor is based around a repository that can be held in any relational database. It stores metadata about the source and target databases, details of the mappings (called “Interfaces” in Data Conductor), the process flows and details of the execution results. [...]

]]> http://www.rittmanmead.com/2006/10/11/oracle-buy-sunopsis/comment-page-1/#comment-1529 Mark Rittman » Getting Started with Sunopsis Data Conductor Sun, 26 Nov 2006 08:28:11 +0000 http://www.rittmanmead.com/wp2/2006/10/11/oracle-buy-sunopsis/#comment-1529 [...] If you were reading this blog a month or so ago, you may well have seen a posting about Oracle’s purchase of Sunopsis. Sunopsis are a French company with offices around the world that specializes in ETL tools; Oracle have bought them because they bring to Oracle the ability to load and transform data on all data platforms, not just the Oracle database, whilst keeping to the current OWB philosophy of using the database as the ETL engine, rather than using a separate ETL hub with it’s own language, database and so on. [...] [...] If you were reading this blog a month or so ago, you may well have seen a posting about Oracle’s purchase of Sunopsis. Sunopsis are a French company with offices around the world that specializes in ETL tools; Oracle have bought them because they bring to Oracle the ability to load and transform data on all data platforms, not just the Oracle database, whilst keeping to the current OWB philosophy of using the database as the ETL engine, rather than using a separate ETL hub with it’s own language, database and so on. [...]

]]>