Mallikarjun n Channappagoudra


I have a package that I was able to edit a week before. But now it is consuming all CPU memory (100%) and not letting me to edit the package (When I try to edit that it says Visual Studio Is busy even after an hour waiting).

Even though I have not changed anything, the package is behaving like this.

I would appreciate any reply on this

Thanks in advance




Re: Package taking 100% of the CPU when it is opened for editing in visual studio

Bob Bojanic - MSFT


What has changed between two runs Did you install anything on your machine What is the packaged doing -- any dependancy on external resources

Thanks,

Bob







Re: Package taking 100% of the CPU when it is opened for editing in visual studio

Mallikarjun n Channappagoudra

Hello Bob,
Thanks for your interest.

No change between two runs and I have not installed/Uninstalled any thing.
All other packages are working fine but only that package is taking lot of time.
Today I able to open the package and even able to select the components(Transformations) but It takes lot of time to respond.Around 5 minutes it takes if I switch from one dataflow to another.






Re: Package taking 100% of the CPU when it is opened for editing in visual studio

Bob Bojanic - MSFT

You have to figure out what is causing this delay. Copy your package into an temporary file and start cutting it piece by piece.

There is not much help we can offer you based on the amount of information you provided. Try to nail down your issue and come back with a more specific question.

Thanks,

Bob






Re: Package taking 100% of the CPU when it is opened for editing in visual studio

BigPlayer

I have the same issue, was there ever a resolution to this



Re: Package taking 100% of the CPU when it is opened for editing in visual studio

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.