Consider the following scenario:
- You have a Microsoft SQL Server 2005 Integration Service (SSIS 2005) or Microsoft SQL Server 2008 Integration Service (SSIS 2008) package that uses the IBM DB2 OLE DB provider to connect to an IBM DB2 server.
- This package exports data from SQL Server 2005 or SQL Server 2008 to a table that is located on the IBM DB2 server. The table contains many rows.
- You try to run the package.
In this scenario, you cannot run the package successfully, and you receive the following exception:
Package Error
Error Source: Microsoft Cursor Engine
Error Description: The number of failing rows exceeds the maximum specified.
Out of memory
IBM DB2 does not support a server-side, forward-only, updatable cursor. Therefore, the IBM DB2 OLE DB provider creates a client-side cursor by using Microsoft OLE DB Cursor Engine. When a server-side, forward-only, updatable cursor is requested, Cursor Engine tries to create a client-side, updatable cursor. This behavior causes Cursor Engine to fetch every row from the table that is located on the IBM DB2 server before SQL Server regains control. This operation uses lots of memory. This high memory usage causes the exception.
SQL Server 2005
The fix for this issue was first released in Cumulative Update 7 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:
976951Â
(http://kbalertz.com/Feedback.aspx?kbNumber=976951/
)
Cumulative update package 7 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. Microsoft recommends 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.
SQL Server 2008
Release version of SQL Server 2008
The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
977444Â
(http://kbalertz.com/Feedback.aspx?kbNumber=977444/
)
Cumulative update package 9 for SQL Server 2008
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 2008 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:
956909Â
(http://kbalertz.com/Feedback.aspx?kbNumber=956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released
SQL Server 2008 SP1
The fix for this issue was first released in Cumulative Update 6 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
977443Â
(http://kbalertz.com/Feedback.aspx?kbNumber=977443/
)
Cumulative update package 6 for SQL Server 2008 Service Pack 1
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 2008 fix release. Microsoft recommends 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:
970365Â
(http://kbalertz.com/Feedback.aspx?kbNumber=970365/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
To work around this problem, use one of the following methods.
Method 1Create an empty view that selects data from the table that is located on the IBM DB2 server. Then, use the SSIS 2005 or SSIS 2008 package to export data from SQL Server 2005 or SQL Server 2008 to this view. Do not export the data to the table directly.
For example, run a statement that resembles the following:
CREATE VIEW Test AS SELECT * FROM <Destination table> WHERE 1=2
Use Microsoft IBM DB2 Provider instead of the IBM DB2 OLE DB provider.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more 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