When a database connection error occurs while the Integration Service is executing a SQL query for an input row, the Integration Service attempts to reconnect to the database.
Use the following rules and guidelines for resiliency in query mode:
When the Integration Service is executing the first query in a list, and a database connection failure occurs, the Integration Service re-executes the first query in the list for the row. It executes the rest of the queries for that row.
If the first query statement is a SELECT statement and a communication failure occurs after some rows are flushed downstream in the pipeline, the session fails.
If a connection failure occurs while the Integration Service is executing a query that not the first query in a list, the Integration Service re-connects to the database and skips the rest of the queries for the current row. Query results might be lost for the previous rows.
If the Integration Service is not able to reconnect to the database, the session fails if the SQL transformation is using a static connection. If the SQL transformation is using a dynamic connection, the session continues.
If the SQL query in the list has an explicit commit or rollback statement, any query results that were created after the commit point will be lost when the session continues.