Comments on: SSIS 2008 – Beware of incorrect version stamp in SSMS http://www.ssistalk.com/2010/01/04/ssis-2008-beware-of-incorrect-version-stamp-in-ssms/ Random thoughts and experiences with SSIS, by Phil Brammer Wed, 25 Jan 2012 10:27:44 -0600 http://wordpress.org/?v=2.9.2 hourly 1 By: Arthur http://www.ssistalk.com/2010/01/04/ssis-2008-beware-of-incorrect-version-stamp-in-ssms/comment-page-1/#comment-19674 Arthur Wed, 20 Apr 2011 18:17:37 +0000 http://www.ssistalk.com/?p=196#comment-19674 A question is if I see 10.0.1600.22 what does this mean? And most importantly if a package was created on SQL Server 2008 SP and then deployed to a box that sits on SP1 will it run? A question is if I see 10.0.1600.22 what does this mean?
And most importantly if a package was created on SQL Server 2008 SP and then deployed to a box that sits on SP1 will it run?

]]> By: Matt Masson http://www.ssistalk.com/2010/01/04/ssis-2008-beware-of-incorrect-version-stamp-in-ssms/comment-page-1/#comment-2220 Matt Masson Mon, 04 Jan 2010 20:10:58 +0000 http://www.ssistalk.com/?p=196#comment-2220 FYI - the problem was that the service's EXE file (MsDtsSrvr.exe) was flagged so that it would only be updated if it was changed in that patch. The patching configuration was updated to make sure that it gets replaced every time (the same as dtexec). I believe the fix will start showing up in 2008 R2 and beyond. FYI – the problem was that the service’s EXE file (MsDtsSrvr.exe) was flagged so that it would only be updated if it was changed in that patch. The patching configuration was updated to make sure that it gets replaced every time (the same as dtexec).

I believe the fix will start showing up in 2008 R2 and beyond.

]]>