Re: DBD for SQL Server

don't over think it. From: "John Adams" <jxad...@ualr.edu> To: "peter" <pe...@phci.ca> Cc: "Kurt Jaeger" <dbi-us...@opsec.eu>, "Rob Dixon" <the.rob.di...@gmail.com>, "Tim Bunce" <dbi-users@perl.org> Sent: Thursday

Re: DBD for SQL Server

Driver for SQL Server on Linux. > > > -- > *From: *"Kurt Jaeger" <dbi-us...@opsec.eu> > *To: *"Rob Dixon" <the.rob.di...@gmail.com> > *Cc: *"Tim Bunce" <dbi-users@perl.org> > *Sent: *Wednesday, 7 S

Re: DBD for SQL Server

org> Sent: Wednesday, 7 September, 2016 10:01:40 Subject: Re: DBD for SQL Server Hi! > I'm wondering why there is no DBD module for Microsoft SQL Server? MS SQL is mostly-compatible with DBD::Sybase, as far as I know. http://search.cpan.org/~mewp/DBD-Sybase-1.15/Sybase.pm#Using_DBD::

Re: DBD for SQL Server

We connect to SQL Server from Linux at work using DBD::ODBC and the FreeTDS driver. I think that combination gives you the greatest amount of support. Keith Carangelo On Wed, Sep 7, 2016 at 10:01 AM, Kurt Jaeger wrote: > Hi! > > > I'm wondering why there is no DBD module

Re: DBD for SQL Server

On 06/09/16 14:40, Rob Dixon wrote: Hey Tim I'm wondering why there is no DBD module for Microsoft SQL Server? Is it a technical impossibility, or is it just waiting to be written? Thank you, Rob Dixon Norfolk England Microsoft has aligned itself with ODBC in the past and has reaffirmed

Re: DBD for SQL Server

Hi! > I'm wondering why there is no DBD module for Microsoft SQL Server? MS SQL is mostly-compatible with DBD::Sybase, as far as I know. http://search.cpan.org/~mewp/DBD-Sybase-1.15/Sybase.pm#Using_DBD::Sybase_with_MS-SQL > Is it a technical impossibility, or is it just waiting to be written?

DBD for SQL Server

Hey Tim I'm wondering why there is no DBD module for Microsoft SQL Server? Is it a technical impossibility, or is it just waiting to be written? Thank you, Rob Dixon Norfolk England

Re: DBD::Sybase and $sth-{syb_result_type} v. DBD::ODBC (Sql Server)

this information. If you made it this far and are thinking Too bad he didn't ask about OUTPUT parameters, I'll throw that one out too: How do I get the OUTPUT parameters from a stored procedure via ODBC to Sql Server? (Under DBD::Sybase, I'd see $sth-{syb_result_type} == CS_PARAM_RESULT

Re: DBD::Sybase and $sth-{syb_result_type} v. DBD::ODBC (Sql Server)

throw that one out too: How do I get the OUTPUT parameters from a stored procedure via ODBC to Sql Server? (Under DBD::Sybase, I'd see $sth-{syb_result_type} == CS_PARAM_RESULT (), but no such luck with Sql Server, yet.) -Rob Rob Biedenharn http://agileconsultingllc.com [EMAIL

DBD::Sybase and $sth-{syb_result_type} v. DBD::ODBC (Sql Server)

out hope for a way to determine this information. If you made it this far and are thinking Too bad he didn't ask about OUTPUT parameters, I'll throw that one out too: How do I get the OUTPUT parameters from a stored procedure via ODBC to Sql Server? (Under DBD::Sybase, I'd see $sth

DBD::ODBC - SQL Server - odbc_err_handler - inconsistent results

All, Several days ago, I learned how to use the odbc_err_handler subroutine provided by DBD::ODBC... in order to capture the 'message' spit out for non-DDL/DML commands in a SQL Server, such as 'backup' or 'dbcc'. The first batch of commands tested were a variety of backup commands and then DBCC

Re: DBD::ODBC - SQL Server - odbc_err_handler - inconsistent results

Louise, [EMAIL PROTECTED] wrote: All, Several days ago, I learned how to use the odbc_err_handler subroutine provided by DBD::ODBC... in order to capture the 'message' spit out for non-DDL/DML commands in a SQL Server, such as 'backup' or 'dbcc'. The first batch of commands tested were a

RE: DBD::ODBC - SQL Server - odbc_err_handler - inconsistent results

:[EMAIL PROTECTED] Sent: Thursday, December 11, 2003 11:19 AM To: Mitchell, Louise M Cc: [EMAIL PROTECTED] Subject: Re: DBD::ODBC - SQL Server - odbc_err_handler - inconsistent results Louise, [EMAIL PROTECTED] wrote: All, Several days ago, I learned how to use the odbc_err_handler subroutine

DBD::ODBC SQL Server problem

Anyone can point me in the right direction regarding the below error. Using the latest DBI and DBD::ODBC, when one connection is open and two different statement handles are prepared and executed, the second statement handle throws this exception... Connection is busy with results for another

RE: DBD::ODBC SQL Server problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You have two active statement handles and SQL Server does not support multiple active statements with the standard cursor. i.e. you are attempting to issue a query under a connection whilst you still have another active query (under the same

RE: DBD::ODBC SQL Server problem

Deja vu all over again. On Thu, 2002-10-31 at 19:52, [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You have two active statement handles and SQL Server does not support multiple active statements with the standard cursor. i.e. you are attempting to

Re: DBD::ODBC SQL Server problem

One for the FAQ I think - if it's not there already. Tim. On Thu, Oct 31, 2002 at 08:52:43AM -, [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You have two active statement handles and SQL Server does not support multiple active statements with the standard

RE: DBD::ODBC SQL Server problem

Definitely:-) -Original Message- From: Tim Bunce [mailto:Tim.Bunce;pobox.com] Sent: Thursday, October 31, 2002 4:26 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: DBD::ODBC SQL Server problem One for the FAQ I think - if it's not there already. Tim. On Thu, Oct 31, 2002

DBD::ODBC SQL Server problem

Using the latest DBI and DBD::ODBC to connect to SQL Server I'm getting this error... Connection is busy with results for another hstmt (SQL-S1000)(DBD: st_execute/SQLExecute err=-1) This happens when I use the same database handle to execute two different statements. When I open two

RE: DBD-ODBC SQL Server 2000 and Transaction Control

-ODBC SQL Server 2000 and Transaction Control Hello, I am using Active State Perl 5.6.1 and DBD::ODBC to do some inserts on a SQL Server 2000 Database. I would like to have Transaction handling. I tried using Autocommit = 0. I tried using $dbh-do('BEGIN TRANSACTION' ) and $dbh-commit. $dbh-do

DBD-ODBC SQL Server 2000 and Transaction Control

Hello, I am using Active State Perl 5.6.1 and DBD::ODBC to do some inserts on a SQL Server 2000 Database. I would like to have Transaction handling. I tried using Autocommit = 0. I tried using $dbh-do('BEGIN TRANSACTION' ) and $dbh-commit. $dbh-do( 'BEGIN TRANSACTION' ) and $dbh-( 'COMMIT

RE: DBD-ODBC SQL Server 2000 and Transaction Control

Ravi, AutoCommit = 0 and $dbh-commit() (or, of course, $dbh-rollback()) (Case sensitive AutoCommit) Jeff -Original Message- From: Ravishankar Narasimhan [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 31, 2002 6:04 PM To: [EMAIL PROTECTED] Subject: DBD-ODBC SQL Server 2000

Only return the FIRST field from DBD/ODBC/Sql Server stored procedure

I use DBD::ODBC with Easysoft ODBC bridge to connect SQL server 6.5 from Linux. I have a stored procedure that is supposed to return several fields. It only returns the first field of my result set. I searched the archive of this mailing list and haven't found some encouraging news. The book

RE: Only return the FIRST field from DBD/ODBC/Sql Server stored proce dure

-Original Message- From: Guangzu Wang (Houston) [mailto:[EMAIL PROTECTED]] Sent: Monday, June 04, 2001 3:57 AM To: [EMAIL PROTECTED] Subject: Only return the FIRST field from DBD/ODBC/Sql Server stored proce dure I use DBD::ODBC with Easysoft ODBC bridge to connect SQL server

RE: Only return the FIRST field from DBD/ODBC/Sql Server stored p roce dure

Thanks, Neil. -Original Message- I use DBD::ODBC with Easysoft ODBC bridge to connect SQL server 6.5 from Linux. I have a stored procedure that is supposed to return several fields. It only returns the first field of my result set. I searched Not sure what you mean. What does

RE: Only return the FIRST field from DBD/ODBC/Sql Server stored proce dure

-Original Message- From: Neil Lunn [mailto:[EMAIL PROTECTED]] Sent: Sunday, June 03, 2001 8:44 PM To: 'Guangzu Wang (Houston)'; [EMAIL PROTECTED] Subject: RE: Only return the FIRST field from DBD/ODBC/Sql Server stored proce dure -Original Message- From: Guangzu Wang

RE: Only return the FIRST field from DBD/ODBC/Sql Server stored proce dure

-Original Message- From: Sterin, Ilya [mailto:[EMAIL PROTECTED]] Sent: Monday, June 04, 2001 1:02 PM To: Neil Lunn; 'Guangzu Wang (Houston)'; [EMAIL PROTECTED] Subject: RE: Only return the FIRST field from DBD/ODBC/Sql Server stored proce dure @list = $sth-fetchrow_array

DBD::ODBC SQL Server 7

I have a particular problem fetching information: Server is running Microsoft SQL Server 7, OpenLink DAD Server Software, Win NT 4.0 Client is a debian box running odbcsdk drivers (detects them as iODBC). I successfully connect through the examples, and successfully retrieve data. I then try