Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.

Symptoms

You create or edit a Microsoft SQL Server 2008 Integration Services (SSIS) package in Business Intelligence Development Studio (BIDS). You edit an OLE DB source in a Data Flow task. When you click the Columns tab, you receive the following error message:

TITLE: Microsoft Visual Studio

------------------------------

Error at Data Flow Task [OLE DB Source [1]]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E21.

------------------------------

ADDITIONAL INFORMATION:

Exception from HRESULT: 0xC0202009 (Microsoft.SqlServer.DTSPipelineWrap)

Note The DTS_E_OLEDBERROR error code has many causes. This article describes only one rare problem that has a specific cause. To make sure that you are encountering this problem, see the "More Information" section for a troubleshooting method.

Note This problem does not occur in SQL Server 2005.

Cause

In SQL Server 2008 SSIS, a specific check determines whether the identifiers that are used by an OLE DB provider are case-sensitive. This check allows for SSIS to follow the case-sensitivity that is defined by an OLE DB provider configuration when SSIS lists object names, table names, and column names. This check is performed by implementing an OLE DB property that is named DBPROP_IDENTIFIERCASE. However, not all OLE DB providers support and implement this property. If the property is not implemented, an error may occur in the BIDS.

Resolution

Cumulative update information

The release version of SQL Server 2008

Important You must install this cumulative update package if your computer is running the release version of SQL Server 2008.

The fix for this issue was first released in Cumulative Update 5. 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:

969531 Cumulative update package 5 for SQL Server 2008Note 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 The SQL Server 2008 builds that were released after SQL Server 2008 was released

SQL Server 2008 Service Pack 1

Important You must install this cumulative update package if your computer is running SQL Server 2008 Service Pack 1.


The fix for this issue was also later released in Cumulative Update 3 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:

971491 Cumulative update package 3 for SQL Server 2008 Service Pack 1Note 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 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.


This hotfix changes the behavior of the OLE DB source in SSIS to request the DBPROP_IDENTIFIERCASE property. After you apply this fix, SSIS ignores the failure of the DBPROP_IDENTIFIERCASE property. Instead, SSIS uses a default value for the identifiers. After you apply this hotfix, if the OLE DB provider does not implement the property, the identifiers are case-sensitive by default.

Status

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

More Information

Troubleshooting

To make sure that you are encountering this problem, follow these steps:

  1. Download and install the OLE DB Rowset Viewer Sample tool. For more information, visit the following Microsoft Developer Network (MSDN) Web site:

    http://msdn.microsoft.com/en-us/library/ms714336(VS.85).aspx

  2. Start Rowset Viewer.

  3. On the File menu, click Full Connect.

  4. Select the provider, the source, the login, and the other connection string attributes. Then, click OK.

  5. After the connection is successfully completed, on the DataSource menu, point to IDBPProperties, and then click GetProperties.

  6. In the PropSet list, select DBPROPSET_DATASOURCEINFO.

If the DBPROP_IDENTIFIERCASE property is not listed as an available property, or if the DBPROP_IDENTIFIERCASE property has a green question mark next to the property, the provider does not support this property. In this situation, you will encounter the problem that the "Symptoms" section describes.

Steps to reproduce the problem

  1. In SQL Server 2008 BIDS, create a new SSIS package.

  2. Add a Data Flow task to the package.

  3. Add an OLE DB Source component in the Data Flow task.

  4. Configure Connection Manager to use an OLE DB provider that does not support the DBPROP_IDENTIFIERCASE property.

  5. Select a table, a view, or a SQL command, and then provide the required object name or SQL command.

  6. In the left pane, click the Columns tab.

You receive the error message that the "Symptoms" section describes.

References

For more information about the DBPROP_IDENTIFIERCASE property, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn.microsoft.com/en-us/library/ms713637(VS.85).aspxFor more information about the IDBProperties::GetProperties method that is used to query the property value, visit following Microsoft Web site:

http://msdn.microsoft.com/en-us/library/ms714344(VS.85).aspxFor 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 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

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:

822499New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×