tags:

views:

175

answers:

4

I am developing an SQL Server Integration Services package. I have been doing some major refactoring to this package, and now the designer is running really slowly. Even moving components around the screen causes the designer to hang for 2-3 minutes. Looking at the task manager Visual Studio is consuming around 80% of the CPU during this period.

Does anyone have any ideas about this slow performance?

A: 

BIDS has always been a little shall we say 'bloated' You need at least 2GB of RAM on your machine so that you can do stuff. Once it starts up I usually have no problem and sometimes have 2 instances open

I would say start shutting down any programs and services you don't need while using BIDS

SQLMenace
+1  A: 

How big is your package? Are you attempting to perform a whole ETL in a single package?

It helps to keep your packages small, and manage the orchestration in a master package.

This helps with SCC as well.

Edit: To call one package from another, the standard way is to use an "Execute Package Task" from the toolbox. However, with very large sets of packages this too can become cumbersome and it can become easier to use NAnt/MSbuild to manage the orchestration.

Chris Needham
Chris - thanks for your response. Yes - the package in question is relatively large. Have you any suggestions about how to manage the master-child package relationship - given that it is not possible to call one package from another?
Hugh Mullally
A: 

Are you using BIDS helper?

I have found that it can sometimes get corrupted and slow down the whole of visual studio.

Uninstalling and reinstalling BIDS helper has fixed this for me.

Tom Ferguson
A: 

http://sqlblog.com/blogs/jorg_klein/archive/2010/01/04/ssis-package-design-pattern-for-loading-a-data-warehouse.aspx

"This parent/child package design pattern for loading a Data Warehouse gives you all the flexibility and functionality you need."

HTH, Josh

Josh

related questions