Hello,
I've got a question about the MSSQL Writer. We currently have a Writer set up for one database and this writer contains about ~100 tables that run on a daily basis.
However we've run into an issue where if one of the tables fails, then only the preceeding tables are written into the database and the ones that are set up after the table that failed are not.Â
Is there any way to replicate the Orchestrations feature "Continue on Failure" in the MSSQL Writer? Or is it Keboola best practice to separate one big writer into multiple writers, so that only a subset of tables will not be written into the database (We'd like to avoid this due to the sheer number of tables, and it does not solve the underlying issue)?