Thanks for your response, Drew.  After some brainstorming with a coworker, we came up with a potential solution that looks like it is going to work and be much, much...

Thanks Hugo, that definitely helps. I need to try a couple of tweaks with this information in mind to make sure I'm getting consistent results (and maybe better throughput...

Thanks for all of the responses. Lots of interesting ideas. The computed column approach is probably the most elegant, but it was met with a resounding "Nope" when...

So here's what I came up with (thanks for the nudge in the right direction, all). I think this will do the trick.

Lookup table:

CREATE TABLE [dbo].[Target_Value_Map](

[map_rule_sequence_no] [int] NOT...

Thanks again, Eirikur. I've been thinking along similar lines as far as how the table structures would look. The fun part (as Phil suggested) is figuring out how...

Thanks for the replies. I forgot to mention one further complication that does occur in the real data: You can see the same value in different source columns, but...

Hi NewBi

I tried your approach of deleting and copying the packages back over. Did not make any difference. Thanks though.

Why would SQL Server Agent need a restart? Just to clarify, these packages are being executed via the Windows Scheduler, not via SQL Server Agent jobs.

Thanks for the additional ideas. It definitely seems to be a problem with the configuration. I added some code to capture the values assigned to variables in the...

Thanks for the responses. It definitely seems like it could be caching at work here. Fits all the symptoms we've been seeing. I have restarted the Task...

More weirdness: If I run the scheduled job manually (right-click on the job in the list of windows scheduled jobs) and run it, it works fine. But if...

Thanks for responding. The configurations use environment variables on the server. Those variables have been updated correctly, and the packages pick up the updated values when viewed/executed in...

Issue resolved. Even though this is supposedly not a network share, I was able to get the package to run from the agent by replacing the drive letter reference...

Thanks for the response Tim. I'd rather not mess with the directory names, because at this point I don't know what the impact of such a change would be...

Check out the SQL 2000 DTS Designer for SQL Server 2005. It can be installed as part of the "Feature Pack" found in the link below:

http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

This might...