If you have several dozen SSIS packages and you don’t have some sort of naming or placement scheme to make sure you know what version each package is you could easily get into trouble. This can lead to some problems if you are supporting multiple versions of SSIS. And you certainly can’t open an SSIS package from a later version than the tool you are opening it with. The only option to downgrade the package is if you have a backup or an older copy. Once it’s upgraded there is no going back. If you open a lower version of SSIS in the tool for a higher version (Data Tools or Business Intelligence Development Studio) then the package is upgraded. When editing, however, there is no backward (or forward) compatibility at all. Later versions of dtexec will “temporarily” upgrade a package in order to run it in their version. On the execution side things aren’t too bad. One of those is just how version specific it is. Unfortunately some of the biggest complaints I had back in the beginning I still have today. Certainly the recent versions of SSIS have shown huge improvements. It is a very powerful and useful tool that can do some amazing things. When SSIS first came out there were huge numbers of jokes and posts about all of the problems and how everyone thought DTS was much better and did they really have to switch? Over the years I’ve come to appreciate SSIS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |