Re: Common problems calling procedures in MS SQL Server via DBD::ODBC

From: "Martin J. Evans" <[email protected]>
> I've written up some of the issues causing confusion on dbi-users (and 
> to me personally) with DBD::ODBC and MS SQL Server here:
> 
> http://www.martin-evans.me.uk/node/58
> 
> I encourage all feedback.

SET NOCOUNT ON

and most of the resultsets with zero columns are gone. It's a good 
idea anyway as it conserves some resources that would otherwise be 
wasted on providing the data you are not interested in.

And I don't think "doesn't batch the statements" is a good way to 
explain this. If the INSERT/UPDATE/DELETE happened to be inside a 
loop, you'd get as many resultsets as the number of iterations. And 
you do not "move from one (statement) to the next" by calling the 
SQLMoreResults, you merely move from the RESULTS of one to the 
RESULTS of the other. MSSQL AFAIK doesn't wait till you process the 
results before it starts processing the next statement.

Jenda
===== [email protected] === http://Jenda.Krynicky.cz =====
When it comes to wine, women and song, wizards are allowed 
to get drunk and croon as much as they like.
	-- Terry Pratchett in Sourcery