FIX: SSIS does not transfer a Flat File source data if the delimiter consists of two characters in SSIS 2008 R2 or SSIS 2008

Article translations Article translations
Article ID: 2576118
Microsoft distributes Microsoft SQL Server 2008 R2 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 R2 fix release.
Expand all | Collapse all

On This Page


This article applies to the following product:
  • Microsoft SQL Server 2008 R2 Integration Services
  • Microsoft SQL Server 2008 Integration Services

Symptoms

Consider the following scenario:
  • You install Microsoft SQL Server 2008 R2 Integration Services (SSIS 2008 R2) or Microsoft SQL Server 2008 Integration Services (SSIS 2008) on a computer.
  • You run an SSIS package to transfer the data from a Flat File source.
  • You use a delimiter that consists of two characters on the Flat File source.

    For example, you use the "{{" characters as the delimiter.
  • The Flat File source contains some empty columns.
In this scenario, the SSIS package does not transfer the Flat File source data.

Cause

This issue occurs because the parser that parses the Flat File source uses incorrect characters as the delimiter.

When the delimiter consists of two characters, and when the Flat File source contains some empty columns, the parser uses incorrect characters as the delimiter.

For example, the parser reads the middle two characters instead of the last two characters after you set the delimiter to the "{{{{" characters. Therefore, an internal error is generated, and the issue that is mentioned in the "Symptoms" section occurs.

Resolution

Cumulative update information

Cumulative update 11 for SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 11. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
2834048 Cumulative update package 11 for SQL Server 2008 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 2008 Service Pack 3 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:
2629969 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2591748 Cumulative Update package 3 for SQL Server 2008 R2 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 R2 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:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 R2

The fix for this issue was first released in cumulative update package 9. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2567713 Cumulative update package 9 for SQL Server 2008 R2
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 R2 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:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

Status

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

References

For more information about Flat File sources, visit the following MSDN website:
General information about Flat File sources
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 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:
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 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 2576118 - Last Review: May 20, 2013 - Revision: 3.0
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2576118

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com