Datometry Hyper-Q executes Teradata full table DELETE statements (DELETE FROM table ALL and DELETE FROM table) as TRUNCATE on Azure Synapse Analytics when they are not part of a transaction.
This optimization follows Azure Synapse guidelines and transaction flow constraints. To learn about performance and transactional differences between DELETE and TRUNCATE, see TRUNCATE TABLE in the Microsoft Azure Synapse documentation.
Transaction context may either be controlled by the client or established by Hyper-Q to provide the atomicity for executing a Teradata MACRO.
Full table DELETE statements are passed through as DELETEs without a WHERE clause when transaction limitations are not met, which may result in slower performance.
Please review the transaction context and revise the source application or scripts if the performance gains for DELETE to TRUNCATE translation are necessary.
Please sign in to leave a comment.