Applies To
SQL Server 2012 Enterprise SQL Server 2012 Developer SQL Server 2012 Enterprise Core SQL Server 2012 Standard SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Enterprise Core - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use) SQL Server 2014 Service Pack 2 - duplicate (do not use) SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use) SQL Server 2016 Service Pack 1 System Center Configuration Manager System Center Configuration Manager (current branch - version 1702) System Center Configuration Manager (current branch - version 1610) Microsoft System Center Configuration Manager (LTSB - version 1606) System Center Configuration Manager (current branch - version 1606)

Symptoms

Consider the following scenario:

  • You use System Center Configuration Manager replication process.

  • The process invokes the bulk copy program utility (BCP) APIs to replicate table data between servers.

  • The table contains an XML data type column.

In this scenario, when the XML file is loaded through BCP, and if the memory sum of all attributes in the XML file is greater than 2 MB, the replication process may fail, and you receive the following error message:

State 42000 - Error 6303 - Message [Microsoft][ODBC Driver 11 for SQL Server][SQL Server]XML parsing: Document parsing required too much memory

Resolution

This problem is fixed in the following cumulative updates for SQL Server:

       Cumulative Update 7 for SQL Server 2016 RTM

       Cumulative Update 4 for SQL Server 2016 SP1

       Cumulative Update 6 for SQL Server 2014 SP2

       Cumulative Update 13 for SQL Server 2014 SP1

       Cumulative Update 9 for SQL Server 2012 Service Pack 3

Note After you install this update, you must enable trace flag 6773 in order to enable this fix. To enable trace flag 6773, see the Trace Flags (Transact-SQL) topic on the Microsoft Developer Network (MSDN) website.

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2016

Latest cumulative update for SQL Server 2014

Latest cumulative update for SQL Server 2012 SP3

Status

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

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Want more options?

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