

For instance, you can define a connection to a SQL Server instance or an Excel file at project-level. A project contains a set of packages and has advanced functionalities compared to a simple package.
#Ssis read xml without root code#
Microsoft provides tools to migrate from an older version of a SSIS packages to a SSIS project containing this package.Ī package can be compared to executable code or a workflow description. So, before SQL Server 2012, only package deployment is available. This mode of deployment overcomes package deployment, which is now referred to « legacy deployment mode ». You cannot deploy projects prior to SQL Server 2012 : project deployment appeared with this version. There are plenty of differences between those two modes : With some basic searching, you will find in Microsoft’s documentation, articles and blog posts that there are two kinds of deliverables when we work with SQL Server Integration Services : we can build and deploy SSIS deliverables either as packages or projects. There is an article on Technet listing ten typical usages of SSIS : Typical Uses of Integration Services. We can easily imagine that building a data warehouse is not the only application SSIS is designed for. Microsoft defines SSIS as a plaftform for building enterprise-level data integration and transformation solutions. Based on our version of SQL Server, we will use either Visual Studio (starting SQL Server 2012) or SQL Server BI Development Studio (before SQL Server 2012). One of them is SQL Server Integration Services, also known as SSIS.īasically, this feature (SSIS) allows us to extract, transform and load data from almost any kind of source to almost any kind of destination : flat file, Excel File, RDBMS.

This DWH can be designed using a set of tools (or features) from Microsoft SQL Server. Nowadays, most mid-size companies have implemented a Data Warehouse (DWH) solution.
