I don't think this is a SSIS problem, nor a metadata problem. You said that when run in Management Studio, the proc returns an empty data set in development (column headers only) and nothing at all in production. This is your issue, the fact that it's possible for the proc to return nothing rather than an empty data set, and this is why SSIS is complaining about the metadata Double check that your proc and data are exactly the same in production and development.
Does every code path return something (i.e. Could something be causing production to hit a code path which returns nothing at all)?
I don't think this is a SSIS problem, nor a metadata problem. You said that when run in Management Studio, the proc returns an empty data set in development (column headers only) and nothing at all in production. This is your issue, the fact that it's possible for the proc to return nothing rather than an empty data set, and this is why SSIS is complaining about the metadata.
Double check that your proc and data are exactly the same in production and development. Does every code path return something (i.e. Could something be causing production to hit a code path which returns nothing at all)?
You pointed me in the right direction. The stored proc was set to not continue on Sundays and Mondays, so when it was kicked off by the package Sunday it didn't get far enough in the proc to generate the metadata, which was created entirely by temp tables. So it 'lost' the metadata.
I moved the day continue-or-not check to the package itself, and let it run once, and now it's happy again. – Valkyrie Dec 30 '10 at 12:13.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.