The logging is used for auditing, and also for incremental index, so we don't want it to be disabled. You might still be able to do (haven't tried myself), but it can be very "hacky" doing so.

Thanks Quan,

As you understand, I try to tune the catalogimport as much as possible. :)

I see that when I import a lot of data through the import, I get a lot of locks, since saving the catalog is using transactions. If the batches are too big, this will lock the database and the users will get lock-errors.

Are there any ways to disable the transactions while importing? And are other parts of the commerce api reading optimistic with (with(nolock) keyword) or pessimistic, so we don't get the lock-errors?

There is no way to disable transaction either :). There are parts of system which are not supposed to be "customized".

Keep in mind that if you have problems with import performance, you can always contact our developer support service, or the expert services for assistance.