All,
There is apparently an issue with BIDS (SSIS development) after SP1 for SQL 2k5 is applied. It involves an issue with Servers running SP1 and packages having been developed with the RTM version of BIDS. There's apparently a date formatting conflict between the two. You can find the problem described in the following blog:
Also, SP1 can cause the SSIS service to fail to start. This error is described here:
Finally, the hotfixes. We have tested them (all the ones listed in the below KB article) on one box and they have apparently worked on that box. Not only is the service starting, but BIDS is now working back at RTM speed and efficiency.
So, if you're having trouble with BIDS / SSIS where you weren't having problems before, SP1 is probably the reason. Hope this helps!
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
There is apparently an issue with BIDS (SSIS development) after SP1 for SQL 2k5 is applied. It involves an issue with Servers running SP1 and packages having been developed with the RTM version of BIDS. There's apparently a date formatting conflict between the two. You can find the problem described in the following blog:
Also, SP1 can cause the SSIS service to fail to start. This error is described here:
Finally, the hotfixes. We have tested them (all the ones listed in the below KB article) on one box and they have apparently worked on that box. Not only is the service starting, but BIDS is now working back at RTM speed and efficiency.
So, if you're having trouble with BIDS / SSIS where you weren't having problems before, SP1 is probably the reason. Hope this helps!
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"