December 1, 2006 at 9:33 am
Background: I administer both SQL Server 2000 and 2005 servers. My desktop has both SS2000 and SS2005 client tools. I recently had a problem with a DTS package on a SS2005 system and the solution was to install SS2005 SP1 on my desktop (to update the client tools). This solved that issue, but has apparently caused a bigger problem.
Issue: Yesterday, I moved a developer's SS2000 DTS package from the SS2000 development server to the SS2000 test server. I made some changes to reflect the new server. The DTS package failed last night. Anyone who has SS2000 and SS2005 with SP1 installed can view the package. Anyone who has SS2000 and SS2005 without SP1 cannot view the package. It appears that having SS2005 SP1 on a system does something to DTS packages so that they can run on SS2005 systems and not on SS2000 systems.
Has anyone else seen this? Does anyone know of any solution other than reimaging my computer and reinstalling the SS2000 and SS2005 client tools without SP1?
-SQLBill
December 1, 2006 at 11:06 am
Since someone still can read the DTS packages, DTS packages are not corrupted. The scenario you described also happened for SQL Server 2000 with different SP.
December 1, 2006 at 11:15 am
But they ARE corrupted, they won't run in SS2000 anymore. They were built on a SS2000 server, they were moved to a SS2000 server. They were editted with SS2000 client tools. They have never been on a SS2005 server. However, I have both client tools (SS2000 w/SP4 and SS2005 w/SP1) on my desktop. The package will no longer run on any SS2000 server, even the original package will not run. Only those who have SS2005 SP1 on their desktop/server can view the package. In SS2000 it is corrupt.
-SQLBill
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply