SQL Server Integration Services (SSIS) is a popular data integration software and also a workflow application very useful to create ETLs and designed to be part of the Business Intelligence tools of Microsoft. In this article, we will discuss the evolution of this software and describe where it is going.
Data Transformation Services in SQL Server 7
Everything started on SQL Server 7 which was released in 1998. This was a simple tool to export and import data and to automate some tasks. The name was Data Transformation Services.
Data Transformation Services in SQL Server 2000
SQL Server 2000 became a very popular database. Microsoft was starting to compete with Oracle and sold some millions of SQL Server licenses around the world. At that time, the Data Transformation Services were handled in the SQL Server Enterprise Manager, which was replaced with SSMS later. Data Transformation Services had some connections and a few tasks.
SQL Server 2005 changed completely the interface to create packages. The name was changed from Data Transformation Services to SQL Server Integration Services. The tool to create packages is not so different from what we have now:
In SSIS 2005, we use to work with the BIDS (Business Intelligence Development Studio) which was the father of the SSDT. BIDS was included in the SQL Server Installer. The tasks, sources, destinations growth dramatically. At that time, it was a serious and professional tool to integrate data.
Overview of ETL Architecture In a data warehouse, one of the main parts of the entire system is the ETL process. ETL is the system that reads data from the source system, transforms the data according to the business logic, and finally loads it into the warehouse. While fetching data from the sources can seem […]