Mallikarjun n Channappagoudra
Hello,
I found the problem after waiting thrice for around 30 minutes to get some control on to edit the package. In first two attempts I had to manually stop the visual studio as it was taking longer than 30 minutes. But in third attempt I could edit the package after 40 minutes of waiting and even then it was taking 2 minutes for a single click.
The problem was all my source connections were replaced By Destination connections. L
Description:
In the package I had two connections one pointing to a source database and another pointing to a destination database (this has different schema than source database).
So now all source DB connections are replaced by destination DB connections.ie Package was referring to a destination database connection but fetching the data from source database connection.
The following figure illustrates it best.
Sorry could insert a picture into the postL
Interesting thing here is the package is not giving any design time errors about referred view not present in the database it is referring to.
Due to some restrictions, I have not run the package to check whether it executes or not. But I did not get why this replacement has been done by itself.
Now I got everything corrected except a dataflow.
Another problem:
For the dataflow I left uncorrected, again the package is behaving in the same manner (consuming all CPU) when I try to fetch the data from a view present in the source database.
But this is not package specific. Whenever I tried to refer to this view from any other package then also same problem occurring. And this problem was not there in the week before run.