Did you set the SQL dialect to MSSQL or Sybase? That LOCK TABLE command is not part of IRIS SQL. I'm not familiar with .NET myself, but found this older code sample (rename to IRISConnection()):

                _tconn = new CacheConnection(connectionString);
                _tconn.SQLDialect = "MSSQL";
                _tconn.Open();

thanks for contributing this @Andreas Schneider! Your testing and feedback will help us build a better product, and we'll likely get most of this out of the way before 2021.2 goes GA 

Thanks @Kevin Chan for helping out (he's the author of the parser piece of LOAD DATA ;-) )

In addition to his comments on the encoding issues, you can also take a look at the %SQL_Diag.Result table which will likely have more detailed error info than what we're able to return through SQL semantics (though we're still working on ways to make it clearer). There's also a %SQL_Diag.Message table with row-level errors, which can help you figure out the reason for individual row failures.

Congratulations!

We're lucky to have airpods as the third place prize. Those were easy to split equally between the tied contestants :-)

This sounds exciting! Do you have a demo video, screenshots or a link to the full product page to make it more tangible?

Here are two examples using Synthea:

• https://github.com/intersystems-community/irisdemo-base-synthea
• https://github.com/grongierisc/synthea-fhir-iris

And two example repositories using LOAD DATA (but not yet ZPM-enabled):

• https://github.com/bdeboe/isc-tpch-script
• https://github.com/bdeboe/isc-adventureworks (using the DWH flavour of this well-known dataset only)

See also this DC article about the subject.

What exactly do you want to "switch back" and why?

an iFind transformation would be helpful if you would sometimes want to query the non-transformed form as well, which I don't think is the case here. Just a computed field and/or @Timothy Leavitt s excellent BuildValueArray() sample would be a simple and effective solution.