Hi Gilberto, from our server-side logs we can see you tried multiple
times and each time our system sent out quite a few megabytes before a
Socket Timeout occurred. Please try a different Browser and possibly
verify network / firewall settings.
Ah, I understand -- Exasol's transaction system will prevent this
scenario, as the initial INSERT into the main log table write-locks that
table until the transaction is ended through rollback or commit, which
happens *after* the SELECT in question. ...
Also thanks for the positive feedback! Regarding your request, could you
elaborate why consecutive RUN_ID values per job/script are important to
you? In the current implementation, the RUN_ID serves as sole
foreign/primary key between the logging tab...
I guess you are referring to the Exasol Data Replication Service. We
pretty much stopped active marketing as it had a strong overlap with the
the cloud scalability feature and there were only few cases the DRS
should be preferred. Also, it would not ...
> I´d assume that IMPORT should work in parallel automatically. If you
import from EXA as data source type, yes. > What surprised me was that
IMPORT did perform slower than CTAS on a 50M copy...Of course
CTAS/INSERT also work in parallel and can do w...
