Sometimes, for any reason, you have to create a SQL Server job that executes a dtsx package given by someone else. You don't know what version of SQL Server Data Tools the developer use to create this package, so you have to target the right SQL Server version to run the package.
First of all, to determine the package version, open the dtsx file in any text editor (I personally use notepad++), and locate the DTS:Name="PackageFormatVersion" property, as you can see in this image:
This table can help you to determine the right version

If you are running a newer version of SSDT, you can save any specific package to run in an older SQL server version with the TargetServerVersion property on the package properties:

Sources:
https://docs.microsoft.com/en-us/sql/integration-services/install-windows/installing-integration-services-versions-side-by-side
https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt
https://msdn.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.connectionmanagerbase.targetserverversion.aspx
Thanks for reading!
-Eduardo-
First of all, to determine the package version, open the dtsx file in any text editor (I personally use notepad++), and locate the DTS:Name="PackageFormatVersion" property, as you can see in this image:
This table can help you to determine the right version
If you are running a newer version of SSDT, you can save any specific package to run in an older SQL server version with the TargetServerVersion property on the package properties:
Sources:
https://docs.microsoft.com/en-us/sql/integration-services/install-windows/installing-integration-services-versions-side-by-side
https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt
https://msdn.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.connectionmanagerbase.targetserverversion.aspx
Thanks for reading!
-Eduardo-
Comments
Post a Comment