RE: perl DBI on windows 64

2008-03-18 Thread Ramakrishna Raju
gt; -Original Message- > From: Martin Evans [mailto:[EMAIL PROTECTED] > Sent: Friday, March 14, 2008 4:07 AM > To: dbi-users@perl.org > Subject: Re: perl DBI on windows 64 > > Ramakrishna Raju wrote: > >> Alexander, >> >> t-SQL has a print

Re: perl DBI on windows 64

2008-03-18 Thread Alexander Foken
ent: Friday, March 14, 2008 4:07 AM To: dbi-users@perl.org Subject: Re: perl DBI on windows 64 Ramakrishna Raju wrote: Alexander, t-SQL has a print command and lot of stored procs have print statements in the code to indicate progress of execution or whatever. I need to capture it and

RE: perl DBI on windows 64

2008-03-18 Thread Ramakrishna Raju
March 14, 2008 4:07 AM To: dbi-users@perl.org Subject: Re: perl DBI on windows 64 Ramakrishna Raju wrote: > Alexander, > > t-SQL has a print command and lot of stored procs have print > statements in the code to indicate progress of execution or whatever. > I need to captu

RE: perl DBI on windows 64

2008-03-14 Thread Ramakrishna Raju
, March 14, 2008 4:07 AM To: dbi-users@perl.org Subject: Re: perl DBI on windows 64 Ramakrishna Raju wrote: > Alexander, > > t-SQL has a print command and lot of stored procs have print > statements in the code to indicate progress of execution or whatever. > I need to capture it

Re: perl DBI on windows 64

2008-03-14 Thread Alexander Foken
On 14.03.2008 11:48, Martin Evans wrote: Alexander Foken wrote: On 14.03.2008 09:46, Martin Evans wrote: Alexander Foken wrote: There is one annoyance with SQL server: You can't have more than one "active" statement, i.e. a statement that is executing but not yet finished, per connection. Th

Re: perl DBI on windows 64

2008-03-14 Thread Martin Evans
Alexander Foken wrote: On 14.03.2008 09:46, Martin Evans wrote: Alexander Foken wrote: There is one annoyance with SQL server: You can't have more than one "active" statement, i.e. a statement that is executing but not yet finished, per connection. This is a limitation of the SQL server prot

Re: perl DBI on windows 64

2008-03-14 Thread Alexander Foken
On 14.03.2008 09:46, Martin Evans wrote: Alexander Foken wrote: There is one annoyance with SQL server: You can't have more than one "active" statement, i.e. a statement that is executing but not yet finished, per connection. This is a limitation of the SQL server protocol, not a DBI limitati

Re: perl DBI on windows 64

2008-03-14 Thread Martin Evans
n J. Evans Easysoft Limited http://www.easysoft.com -Original Message- From: Alexander Foken [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 2:41 PM To: Ramakrishna Raju Cc: dbi-users@perl.org Subject: Re: perl DBI on windows 64 On 13.03.2008 19:49, Ramakrishna Raju wrote:

Re: perl DBI on windows 64

2008-03-14 Thread Martin Evans
Alexander Foken wrote: On 13.03.2008 19:49, Ramakrishna Raju wrote: And now, I am looking for a web link or a short snippet that does robust error handling of SQL errors. Use the RaiseError DBI attribute, preferably during connect(). And how to process the output of sql print statements.

Re: perl DBI on windows 64

2008-03-14 Thread Martin Evans
[mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 12:28 PM To: dbi-users@perl.org Subject: Re: perl DBI on windows 64 Sorry for the mess of replying but for some reason my email client won't include your text when it was added after my signature. There are 2 odbc administrators - one you

RE: perl DBI on windows 64

2008-03-13 Thread Ramakrishna Raju
o put something together and then we can compare notes. Thanks, Ramakrishna Raju ( "Raju" ) [EMAIL PROTECTED] -Original Message- From: Alexander Foken [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 2:41 PM To: Ramakrishna Raju Cc: dbi-users@perl.org Subject: Re: perl DB

Re: perl DBI on windows 64

2008-03-13 Thread Alexander Foken
On 13.03.2008 19:49, Ramakrishna Raju wrote: And now, I am looking for a web link or a short snippet that does robust error handling of SQL errors. Use the RaiseError DBI attribute, preferably during connect(). And how to process the output of sql print statements. SQL does not print

RE: perl DBI on windows 64

2008-03-13 Thread Ramakrishna Raju
m: Martin Evans [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 12:28 PM To: dbi-users@perl.org Subject: Re: perl DBI on windows 64 Sorry for the mess of replying but for some reason my email client won't include your text when it was added after my signature. There are 2 odbc admi

Re: perl DBI on windows 64

2008-03-13 Thread Martin Evans
Sorry for the mess of replying but for some reason my email client won't include your text when it was added after my signature. There are 2 odbc administrators - one you get to in the normal way through control panel, administrative tools, data sources (the 64 bit one) and one you have to go t

RE: perl DBI on windows 64

2008-03-13 Thread Ramakrishna Raju
> > > I applied the latest DBD-ODBC 1.15 version (Martin J Evans) > and it still is a problem. Is there any fix or work around for this > issue? > > > > > > Appreciate your time, > > > > Thanks, > > Ramakrishna Raju ( "Raju" ) > > [EMAIL PROTECTED]

RE: perl DBI on windows 64

2008-03-13 Thread Ramakrishna Raju
: Alexander Foken [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 11:23 AM To: Ramakrishna Raju Cc: dbi-users@perl.org Subject: Re: perl DBI on windows 64 It seems you don't have a valid ODBC data source named xxxsql01. If you are running your script from a web server, it has to be a sy

Re: perl DBI on windows 64

2008-03-13 Thread Martin Evans
Ramakrishna Raju wrote: Hi, I am trying to connect to SQL Server 2005 on a windows 64bit machine from the same machine. And I get this error message: DBI connect(xxxsql01,'sa',...) failed: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver spec

Re: perl DBI on windows 64

2008-03-13 Thread Alexander Foken
It seems you don't have a valid ODBC data source named xxxsql01. If you are running your script from a web server, it has to be a system data source, else it may also be a user data source. And by the way: Are you sure you want to connect as "sa"? That account usually has too many privileges.