blog.bartekr.net/2018/02/28/upgrading-ssis-projects-part-iii

Preview meta tags from the blog.bartekr.net website.

Linked Hostnames

8

Thumbnail

Search Engine Appearance

Google

https://blog.bartekr.net/2018/02/28/upgrading-ssis-projects-part-iii

Upgrading SSIS projects - part III

In the first part of the series I mentioned two methods of upgrading SSIS projects (well - packages, for now) - Application.Upgrade() and Application.SaveAndUpdateVersionToXml(). This post is about the latter.\nThe documentation of the method is also a bit sparse at the moment, but is self-explanatory:\npublic void SaveAndUpdateVersionToXml ( string fileName, Microsoft.SqlServer.Dts.Runtime.Package package, Microsoft.SqlServer.Dts.Runtime.DTSTargetServerVersion newVersion, Microsoft.SqlServer.Dts.Runtime.IDTSEvents events ); the name of the target file - that’s where we save the outcome of the update operation (fileName) the package we want to convert (package) which SSIS version we have in mind (newVersion) an object for the events that happened during the process (events) To load the package I use the Application.LoadPackage() method. It reads package from the file and converts it to the object. Then set target version with the Application.TargetServerVersion and run Application.SaveAndUpdateVersionToXml(). The last thing is to create an empty class for the events, and that’s it.\n



Bing

Upgrading SSIS projects - part III

https://blog.bartekr.net/2018/02/28/upgrading-ssis-projects-part-iii

In the first part of the series I mentioned two methods of upgrading SSIS projects (well - packages, for now) - Application.Upgrade() and Application.SaveAndUpdateVersionToXml(). This post is about the latter.\nThe documentation of the method is also a bit sparse at the moment, but is self-explanatory:\npublic void SaveAndUpdateVersionToXml ( string fileName, Microsoft.SqlServer.Dts.Runtime.Package package, Microsoft.SqlServer.Dts.Runtime.DTSTargetServerVersion newVersion, Microsoft.SqlServer.Dts.Runtime.IDTSEvents events ); the name of the target file - that’s where we save the outcome of the update operation (fileName) the package we want to convert (package) which SSIS version we have in mind (newVersion) an object for the events that happened during the process (events) To load the package I use the Application.LoadPackage() method. It reads package from the file and converts it to the object. Then set target version with the Application.TargetServerVersion and run Application.SaveAndUpdateVersionToXml(). The last thing is to create an empty class for the events, and that’s it.\n



DuckDuckGo

https://blog.bartekr.net/2018/02/28/upgrading-ssis-projects-part-iii

Upgrading SSIS projects - part III

In the first part of the series I mentioned two methods of upgrading SSIS projects (well - packages, for now) - Application.Upgrade() and Application.SaveAndUpdateVersionToXml(). This post is about the latter.\nThe documentation of the method is also a bit sparse at the moment, but is self-explanatory:\npublic void SaveAndUpdateVersionToXml ( string fileName, Microsoft.SqlServer.Dts.Runtime.Package package, Microsoft.SqlServer.Dts.Runtime.DTSTargetServerVersion newVersion, Microsoft.SqlServer.Dts.Runtime.IDTSEvents events ); the name of the target file - that’s where we save the outcome of the update operation (fileName) the package we want to convert (package) which SSIS version we have in mind (newVersion) an object for the events that happened during the process (events) To load the package I use the Application.LoadPackage() method. It reads package from the file and converts it to the object. Then set target version with the Application.TargetServerVersion and run Application.SaveAndUpdateVersionToXml(). The last thing is to create an empty class for the events, and that’s it.\n

  • General Meta Tags

    10
    • title
      Upgrading SSIS projects - part III
    • charset
      utf-8
    • viewport
      width=device-width, initial-scale=1
    • description
      In the first part of the series I mentioned two methods of upgrading SSIS projects (well - packages, for now) - Application.Upgrade() and Application.SaveAndUpdateVersionToXml(). This post is about the latter.\nThe documentation of the method is also a bit sparse at the moment, but is self-explanatory:\npublic void SaveAndUpdateVersionToXml ( string fileName, Microsoft.SqlServer.Dts.Runtime.Package package, Microsoft.SqlServer.Dts.Runtime.DTSTargetServerVersion newVersion, Microsoft.SqlServer.Dts.Runtime.IDTSEvents events ); the name of the target file - that’s where we save the outcome of the update operation (fileName) the package we want to convert (package) which SSIS version we have in mind (newVersion) an object for the events that happened during the process (events) To load the package I use the Application.LoadPackage() method. It reads package from the file and converts it to the object. Then set target version with the Application.TargetServerVersion and run Application.SaveAndUpdateVersionToXml(). The last thing is to create an empty class for the events, and that’s it.\n
    • article:section
      Post
  • Open Graph Meta Tags

    6
    • og:title
      Upgrading SSIS projects - part III
    • og:description
      In the first part of the series I mentioned two methods of upgrading SSIS projects (well - packages, for now) - Application.Upgrade() and Application.SaveAndUpdateVersionToXml(). This post is about the latter.\nThe documentation of the method is also a bit sparse at the moment, but is self-explanatory:\npublic void SaveAndUpdateVersionToXml ( string fileName, Microsoft.SqlServer.Dts.Runtime.Package package, Microsoft.SqlServer.Dts.Runtime.DTSTargetServerVersion newVersion, Microsoft.SqlServer.Dts.Runtime.IDTSEvents events ); the name of the target file - that’s where we save the outcome of the update operation (fileName) the package we want to convert (package) which SSIS version we have in mind (newVersion) an object for the events that happened during the process (events) To load the package I use the Application.LoadPackage() method. It reads package from the file and converts it to the object. Then set target version with the Application.TargetServerVersion and run Application.SaveAndUpdateVersionToXml(). The last thing is to create an empty class for the events, and that’s it.\n
    • og:url
      https://blog.bartekr.net/2018/02/28/upgrading-ssis-projects-part-iii/
    • og:site_name
      BartekR
    • og:type
      article
  • Twitter Meta Tags

    4
    • twitter:title
      Upgrading SSIS projects - part III
    • twitter:description
      In the first part of the series I mentioned two methods of upgrading SSIS projects (well - packages, for now) - Application.Upgrade() and Application.SaveAndUpdateVersionToXml(). This post is about the latter.\nThe documentation of the method is also a bit sparse at the moment, but is self-explanatory:\npublic void SaveAndUpdateVersionToXml ( string fileName, Microsoft.SqlServer.Dts.Runtime.Package package, Microsoft.SqlServer.Dts.Runtime.DTSTargetServerVersion newVersion, Microsoft.SqlServer.Dts.Runtime.IDTSEvents events ); the name of the target file - that’s where we save the outcome of the update operation (fileName) the package we want to convert (package) which SSIS version we have in mind (newVersion) an object for the events that happened during the process (events) To load the package I use the Application.LoadPackage() method. It reads package from the file and converts it to the object. Then set target version with the Application.TargetServerVersion and run Application.SaveAndUpdateVersionToXml(). The last thing is to create an empty class for the events, and that’s it.\n
    • twitter:card
      summary_large_image
    • twitter:image
      https://blog.bartekr.net/2017/12/24/upgrading-ssis-projects-part-i/images/TargetServerVersion2017.png
  • Link Tags

    5
    • canonical
      https://blog.bartekr.net/2018/02/28/upgrading-ssis-projects-part-iii/
    • shortcut icon
      /favicon.ico
    • stylesheet
      /scss/style.min.e8c7fca7d1c9294aa7a4f3426c225ee26540f7d94e39be0b5a4a5c8a49ca5a25.css
    • stylesheet
      https://cdn.jsdelivr.net/npm/[email protected]/dist/default-skin/default-skin.min.css
    • stylesheet
      https://cdn.jsdelivr.net/npm/[email protected]/dist/photoswipe.min.css

Links

32