Sybase DI Suite versus Microsoft SQL server 2005 SSIS for ETL and Datawarehouse
-
Hi,
what would you do if you would be confronted with the following question?
The organisation I currently work for is searching for a datawarehousing solution to collect information from about 8 Microsoft SQL 2005 databases. The advice we have received so far is to use the Sybase Data Integration Suite for the Extraction, Loading and Transformation of all current Microsoft SQL server 2000 and 2005 databases to a centralized Microsoft SQL server 2005 Data Warehouse.
However after reviewing Microsoft SQL server 2005 and BI information, it seems Microsoft also offers the required ETL functionality through the usage of SQL Server Integration Services (SSIS).
What would you recommend?
best regards,
Manolito
-
symbiant2k (2/9/2009)
Hi,what would you do if you would be confronted with the following question?
The organisation I currently work for is searching for a datawarehousing solution to collect information from about 8 Microsoft SQL 2005 databases. The advice we have received so far is to use the Sybase Data Integration Suite for the Extraction, Loading and Transformation of all current Microsoft SQL server 2000 and 2005 databases to a centralized Microsoft SQL server 2005 Data Warehouse.
However after reviewing Microsoft SQL server 2005 and BI information, it seems Microsoft also offers the required ETL functionality through the usage of SQL Server Integration Services (SSIS).
What would you recommend?
best regards,
Manolito
If you are already based on SQL Server 2005, why pay additionally for another ETL toolkit? I don't have knowledge about Sybase DI, but it is clear what would be the more cost-efficient solution.
---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply