You can now use the new connection string parameter 'TrimWhitespaces=false;' to workaround a SQL issue due to leading/trailing whitespaces in the data. This avoids the error "Concurrency violation: the UpdateCommand affected 0 of the expected 1 records".