Microsoft Knowledge Base Email Alertz

Error message when you save a SQL Server 2005 Integration Services package in SQL Server Business Intelligence Development Studio: Exception of type 'System.OutOfMemoryException' was thrown

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 952110 - Last Review: May 1, 2008 - Revision: 1.1

Error message when you save a SQL Server 2005 Integration Services package in SQL Server Business Intelligence Development Studio: "Exception of type 'System.OutOfMemoryException' was thrown"

SYMPTOMS

Consider the following scenario. In Microsoft SQL Server 2005 Integration Services (SSIS), you create an SSIS package. The SSIS package contains some Script tasks or Script components. When the file size of the SSIS package increases to more than 7 megabytes (MB), you receive the following error message when you try to save the SSIS package in SQL Server Business Intelligence Development Studio:
TITLE: Microsoft Visual Studio
------------------------------
Failure saving package.
------------------------------
ADDITIONAL INFORMATION:
Exception of type 'System.OutOfMemoryException' was thrown. (Microsoft.SqlServer.ManagedDTS)
------------------------------
BUTTONS:
OK

CAUSE

This problem occurs because heap memory is fragmented in the SQL Server Business Intelligence Development Studio process.

WORKAROUND

To work around this problem, break up the SSIS package into smaller packages. If you want to provide contiguous workflow in the package design, you can run the child packages from the context of the parent package by using the Execute Package task. Or, run the child packages as separate steps from a SQL Server Agent job.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

This problem does not occur in SQL Server 2008 Integration Services.

APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
Keywords: 
kbtshoot kbexpertiseadvanced kbsql2005ssis kbprb KB952110
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate