https://communities.sas.com/t5/SAS-Programming/SAS-Access-to-Teradata-SQL/m-p/40193#M8150 I am not a user of Teradata but a quick search of SAS support confirms that the default behaviour of Teradata for updates is one row at a time. Suggest you try the DBCOMMIT = option to get Teradata to commit your updates say every 1,000 or 10,000 rows. Also suggest you investigate the Teradata MULTILOAD capability, This will not only improve update performance it will probably reduce query log entries. Check also with your DBA to see if there is a Teradata option for switching off the log messages. Mon, 28 Jun 2010 21:44:50 GMT SASKiwi 2010-06-28T21:44:50Z https://communities.sas.com/t5/SAS-Programming/SAS-Access-to-Teradata-SQL/m-p/40192#M8149 When SAS writes data to teradata tables through SAS/Access to teradata engines, it creates huge number of entries in DBC Query Log.<BR /> <BR /> Is this something to do with the SQL used in SAS. SAS uses ANSI SQL and Teradata's SQL is different. When ever a row of data is added to teradata table, it commits that record and makes an entry into DBC Qyery Log of Teradata?<BR /> <BR /> Can this be stopped? Thu, 24 Jun 2010 16:24:37 GMT https://communities.sas.com/t5/SAS-Programming/SAS-Access-to-Teradata-SQL/m-p/40192#M8149 sahkul 2010-06-24T16:24:37Z https://communities.sas.com/t5/SAS-Programming/SAS-Access-to-Teradata-SQL/m-p/40193#M8150 I am not a user of Teradata but a quick search of SAS support confirms that the default behaviour of Teradata for updates is one row at a time. Suggest you try the DBCOMMIT = option to get Teradata to commit your updates say every 1,000 or 10,000 rows. Also suggest you investigate the Teradata MULTILOAD capability, This will not only improve update performance it will probably reduce query log entries. Check also with your DBA to see if there is a Teradata option for switching off the log messages. Mon, 28 Jun 2010 21:44:50 GMT https://communities.sas.com/t5/SAS-Programming/SAS-Access-to-Teradata-SQL/m-p/40193#M8150 SASKiwi 2010-06-28T21:44:50Z