May 4, 2010 at 11:50 am
Has anyone ever encountered a situation where data source overrides get lost or reset? I have some vendor supplied packages that are hard-coded with the test server name, which when migrated to production, are then overridden (with the production server name) on the data sources tab of the package / job step. This has worked flawlessly for months, until one day last week, the package / job started having all kinds of trouble, due to the fact that on one of the job steps, the override to point to production got lost, and that step started running against the test server (while all of the other steps ran against production).
All interested parties have denied changing anything; is anyone aware of any known bugs or processes that might cause such overrides to be changed or reset?
Thanks.
May 4, 2010 at 12:14 pm
I'm aware of no defects related to that. I would venture to guess that someone did indeed do it and not even realize it. So they aren't lying. It does happen and data rarely gets changed without someone doing it, it might be accidentally but it does happen.
CEWII
May 5, 2010 at 2:34 am
Microsoft itself dissuades the use of data sources between different enviroments:
http://msdn.microsoft.com/en-us/library/cc671619
(maybe the answer to your problem is mentioned somewhere in the article)
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 6, 2010 at 9:56 am
I've found that data source changes can get lost if the job is edited even if you don't touch that bit. You have to tick the box at the left end of the data source line to edit it. I think if you don't it reverts to the original when you next edit the job. It seems a bit woolly and "Help" doesn't help on the subject.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply