Warning for those using Cursors in Microsoft SqlServer with ODBC or ADO

2001-06-15 Thread tim . wilson
Hi all Just thought I'd let you know about a gotcha when using ODBC (and ADO I think) to connect to Microsoft Sqlserver. I now highly recommend having: SET NOCOUNT ON as the first statement in all your stored procedures. I had a cursor inside a stored procedure that ran correctly from isqlw bu

RE: Question regarding dbi:ADO isolation level,Connection and command properties , and streams

2001-06-07 Thread tim . wilson
Thanks for the quick reply, I will probably not have the time to make the changes in the next couple of weeks. But as I am in the position of wanting Perl on NT to talk to multiple data sources and would prefer to use ADO, I will try and make the changes to ado.pm and send it to you. When I can.

Question regarding dbi:ADO isolation level,Connection and command properties , and streams

2001-06-06 Thread tim . wilson
uery (over 9 minutes) was failing with a timeout. I have made a addition to my copy of ado.pm to add this to the %attr that you can pass through on a prepare, and it seems to work. 3. Is there a reason that Stream support should not be added to ADO.pm. Has anyone experimented with