Since its inception, SSIS designer never supported backward compatibility. For example, if you developed a package in SSIS 2014 and tried to deploy it in a SSIS 2012 catalog, you would not be able to do it. Or worse, if you opened a package developed with SSIS 2012 with a SSDT that was used with SSIS 2014, the package was upgraded. When another developer tried to open it with SSDT used for SSIS 2012, he/she was not able to do it. The package was upgraded, period.
With SSIS 2016, SSDT had the following enhancements:
- Backward compatibility to prior SSIS versions down to SSIS 2012.
- Unified SSDT: as we'll see later in the book, SSDT can be used for BI components development as well as database development. Prior to SSDT ...