Whenever I make any attempts at opening an SSIS Package with Visual Studio I get the following message at the foot of the screen:

Following this, the whole environment locks up and becomes totally unusable.

Each day I waste an average of about a hour waiting for these messages to clear.

 

Can you please get back to me with a solution asap.

 

  "Microsoft Visual Studio is Busy - Microsoft Visual Studio is waiting for an internal operation to complete. If you regularly encounter this delay during normal usage, please report this problem to Microsoft."

Hello,

This forum is meant for issues regarding the Visual Studio documentation and Help system.  You'll probably get more reponses to this issue if you post it in one of the forums such as SQL Server Integration Services or Visual Studio Debugger.

That being said, in an effort to try to help you, I did some looking around on the subject and discovered that this, unfortunately, appears to be a fairly common problem with SSIS/BIDS projects in Visual Studio.  It seems to boil down to the following (from comments in this blog):

"We've noticed that the combination of merge joins, lookups and many column dataflows (e.g. several hundred columns) seems to cause an exponential degredation on BIDS. BIDS becomes so slow, just moving a component, let alone making a change to a merge join or something, may cause the design surface to take minutes to refresh and/or you keep getting the infuriating "...visual studio is busy..." message."

Here are some other resources I found that discuss this problem.  I wish I had a good solution for you, but it sounds like it's a bug that should be reported via http://connect.microsoft.com:

http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/9b3a0f26-1e00-46a5-8c75-f818bdf2907f

http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/37748d60-3c8e-4ead-ba19-37d03d8ef4ba
"So, in short, if you get the "Visual Studio is busy" aka the "Microsoft Visual Studio Delay Notification" message, try copying the package and stripping it down to the XML bones and rebuilding it until you find the culprit tags that are giving the parser issues.  Remove them from your XML file, save, and redraw in the designer."

http://www.webservertalk.com/message1332054.html

http://blogs.vertigo.com/personal/bellis/Blog/archive/2007/07/23/sql-server-integration-services-ssis-etls-and-best-practices.aspx

HTH,

---

- Kemp Brown [MSFT]