A related question to a previous one regarding the same subject. In a CLR stored procedure, I am bulding a collection of objects which represent a data set after a complex filtering. This collection is then "translated" in a resulset with the SqlContext.Pipe.SendResultsStart / SendResultsRow / SendResultsEnd loop and delivered.
Despite this works as it should, it doesn't feel optimal because of the loop etc. Are there any better alternatives to, say, convert collections to SQL resultsets on the fly?
Thanks in advance.