CODEWITHSUNDEEP
sqlsql-serverexportdata-export
Tanaka Saito
Tanaka Saito

Reputation: 1100

Increasing MaximumErrorCount for Data Export in SQL Server Management Studio

I have looked at countless other stack posts and random blogs but cannot find where this setting is located.

I have a database on SQL Server 2017 that I want to change the collation on. Because we're using schema-bound objects we cannot just do an ALTER DATABASE MyDatabase COLLATE MyCollation; so we need something else. I tried to follow the guide on this blog post suggesting a backup of keys and indices, drop them, recreate database, import the keys and indices, but as I don't understand enough about cursors and where the @table variable is coming from I moved on from that approach.

My current thinking is that if I can just export the necessary data from the necessary tables, create a new database, and then re-import the data to the new database with the correct collation I should be set. I'm using SSMS and going with Tasks > Export Data... to get the data out from the database with SQL Server Native Client 11.0 as both Source and Destination. When this wizard runs, the first run only gives Status = Success. The second one gives Warnings on Validation. The third run throws Error on Validation:

Warning 0x80049304: Data Flow Task 1: Warning: Could not open global shared memory to communicate with performance DLL; 
data flow performance counters are not available.  
To resolve, run this package as an administrator, or on the system's console.
 (SQL Server Import and Export Wizard)

enter image description here

The thing is, I'm logged in with the SA account. The Copying Rows completes on warnings saying:

Warning 0x80019002: Data Flow Task 3: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. 
This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
 (SQL Server Import and Export Wizard)

The target/destination database only contains some of the tables, presumably because it hit the maximumerrorcount before it could finish.

My question is, where can I increase the MaximumErrorCount?

EDIT: It seems that I'm not the only one having similar issues with data export/import in SSMS

Upvotes: 0

Views: 739

Answers (0)

Related Questions