Keep Inserts and Deletes from returning a recordset

Connectivity

Keep Inserts and Deletes from returning a recordset

I have a Teradata macro that executes multiple SQL commands (such as insert, update, and delete) to populate a Global Temp table before performing the final select.

Our corporate reporting tool will only return one recordset. If the first statement is an insert or a delete Teradata will return a null or blank recordet to our reporting tool and it will ignore all other recordsets.

Is there a way to keep Teradata from returning a recordset for inserts and deletes? I was hoping the .NET Data Provider would have fixed this issue, but it works the same way as ODBC.

How can I keep Teradata from returning a recordset for an insert or delete?

Thanks!
1 REPLY
Teradata Employee

Re: Keep Inserts and Deletes from returning a recordset

TdDataReader class in the .NET Data Provider for Teradata skips DELETE, INSERT and UPDATE results sets and will stop at the very first data-returning (SELECT) statement.