[font="Verdana"]Interesting start to a good topic.

I'm not sure I agree with the comment in the article that the "only way" to do things in the past has been with stored procedures that only take one row. It's been possible to pass XML to a stored procedure for some time now. I see someone has put up some code in the discussion to do precisely that. I believe that typed XML has some performance gains, so that might be a worthwhile comparison.

If your application must "stream" data to SQL Server, have you considered using a queue of some sort (either SQL Server Broker or MSMQ for example.) The overhead for using queues is not inconsiderable, but in some cases it may well be a better approach to having to stream the data.

Anyway, the point being that this is a new solution (and an excellent one) in SQL Server 2008, but by no means the only solution to the issue of having to pass in multiple rows of typed data to SQL Server.

[/font]