SET NOCOUNT OFF - how to capture returned messages
Posted on 2009-05-09
Suppose I SET NOCOUNT OFF in a stored procedure; I know it's not recommended, but just suppose that for a moment.
The stored procedure performs numerous deletes, updates, inserts. After each of those a message is returned to the caller (in this case ADO.NET) containing the number of records affected.
How do I capture, in ADO.NET, such returned messages (a large number of such messages) ??