Consider the following scenario:
- You have a Microsoft SQL Server 2005 Integration Services (SSIS 2005) package.
- The SSIS 2005 package transfers data by using Lookup transformations.
- The Lookup transformations that are in the SSIS 2005 package run in parallel.
- The Lookup transformations are cache enabled and share the same cache area.
- You try to run the SSIS 2005 package.
In this scenario, the tasks of the Lookup transformations crash, and you cannot run the SSIS 2005 package successfully.
When this problem occurs, an access violation occurs, and a mini-dump file is generated in the SQL Server Error Dumps folder. By default, the mini-dump file is generated in the following folder:
%ProgramFiles%\Microsoft SQL Server\90\Shared\ErrorDumps\SQLDmpr<number>.mdmp
When the same cache is used by components that are running in parallel data flows, a failure occurs when the shared cache is synchronized.
Therefore, the problem that is mentioned in the "Symptoms" section occurs.
The fix for this issue was first released in Cumulative Update 9 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
980176Â
(http://kbalertz.com/Feedback.aspx?kbNumber=980176/
)
Cumulative update package 9 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598Â
(http://kbalertz.com/Feedback.aspx?kbNumber=960598/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about Lookup transformations, visit the following Microsoft Developer Network (MSDN) Web site:
For information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897Â
(http://kbalertz.com/Feedback.aspx?kbNumber=935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
913089Â
(http://kbalertz.com/Feedback.aspx?kbNumber=913089/
)
How to obtain the latest service pack for SQL Server 2005
For more information about new features and improvements in SQL Server 2005 Service Pack 3, visit the following Microsoft Web site:
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499Â
(http://kbalertz.com/Feedback.aspx?kbNumber=822499/
)
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates