KB44462: "ERROR: External Table: count of bad input rows reached maxerrors limit ...SQL Statement: insert into xxx values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?).. Error Code= -2147212544." error occurs during bulk export in MicroStrategy 9.4.x-10.x

SUMMARY:
This technical note documents why "ERROR: External Table: count of bad input rows reached maxerrors limit ...SQL Statement: insert into xxx values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?).. Error Code= -2147212544." error occurs during bulk export in Strategy 9.4.x-10.x. A resolution has been provided.
SYMPTOM:
In Strategy 9.4.x-10.x, bulk export fails due to an ODBC error even though the report runs successfully through Strategy Developer 9.4.x-10.x. An error is presented in the DSSErrors.log file and a delivery failure notification is sent to the Administrator with an ODBC error similar to the following:

(QueryEngine encountered error: OdbcParameterizedQuery::ExecQuery failed. Error type: Odbc error. Odbc operation attempted: SQLExecute. Operation canceled ERROR: External Table : count of bad input rows reached maxerrors limit Connection String: DSN=xxxx;DATABASE=xxxx;SERVERNAME=xxxx;UID=xxxx;PORT=xxxx;READONLY=0;SQLBITONEZERO=0;LEGACYSQLTABLES=0; NUMERICASCHAR=0;SHOWSYSTEMTABLES=0;LOGINTIMEOUT=0;QUERYTIMEOUT=0;DATEFORMAT=1; SECURITYLEVEL=preferredUnSecured;CACERTFILE=;. SQL Statement: insert into xxxx values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?).. Error in Process method of Component: QueryEngineServer, Project xxxx, Job 110, Error Code= -2147212544.)

CAUSE:
This error message is because of a parameterized query failing to execute successfully. However, the reason for this to occur can be due to multiple reasons.

1. One potential reason for this error message to occur is if the database that is being used to store the intermediate tables for bulk export does not support parameterized queries. In this scenario, parameterized queries should be disabled on the specific database instance. The following Strategy Knowledge Base technical note explains what parameterized queries are and how to enable/disable them in Strategy:
   
   KB5544 - What is a parameterized query in Strategy Query Engine 9.x?
    
2. If the database supports parameterized queries, this error message can occur due to a failure in the data that is being inserted. 
    

ACTION:
If the database being utilized for bulk export does not support parameterized queries, then parameterized queries should be disabled or the Database Administrator must be contacted to determine why the parameterized query inserts are failing. If the database has been confirmed to support parameterized queries, then parameterized queries should still be disabled, but only for testing purposes while attempting to determine the root cause of the issue. The error message received is not specific as it is only indicating that the parameterized query has failed to execute. It does not give additional information. By disabling parameterized queries, the user would be able to determine what specifically is failing. For instance, inserting data with an inappropriate data type.
Note: Parameterized queries can provide significant performance gains when inserting data into a database. If the database does not support parameterized queries and performance is a concern, moving to a database that provides full support for this functionality may be necessary.