I just thought the problem was so obscure nobody had ideas!  Hehe.  Anyway, to 
answer your questions:

We are parsing out all newlines from the select statement.
As for finding out what the server thinks it's getting...we'll have to dig into 
that.  We don't have direct access to the server, only ODBC.
And finally, we did turn on tracing originally.  It showed that it makes it as 
far as execute, and then both the script and the trace stop.  We have tried all 
different levels of tracing (1-15) with the same results.

This is one of those problems that is going to leave a permanent dent in my 
forehead from repeatedly applying it to the desk.

Thanks for your help!

-Brian



[EMAIL PROTECTED] wrote:
>Since no one else seems to have answered I'll jump in with a few  
>questions that might be helpful.
>
>Does it make any difference if there is an embedded newline in the  
>statement?
>
>Is there a way to query the server to find out what query it thinks  
>it's gotten? I've never worked with MSSQL so I don't know what sort  
>of tools are available.
>
>Can you get any useful information by turning DBI tracing on?
>
>-Chris
>
>On Aug 29, 2007, at 2:16 PM, Brian Johnson wrote:
>
>> Hey folks -
>>
>> We have written an app that makes a connection to a MSSQL server  
>> using ODBC.  It works great as long as the length of our select  
>> statement is 668 characters or less.  As soon as it hits 669  
>> characters, it hangs forever doing the execute.  It also fails if  
>> we use $dbh->do() instead of $dbh->prepare() and $dbh->execute.
>>
>> I have googled like crazy trying to find some direction, but have  
>> come up empty.  Has anybody seen this before?  Or is this something  
>> obvious and I should be hit with a rolled up news paper for not  
>> figuring it out?
>>
>> Thanks.
>>
>> -Brian
>
>-- 
>Christopher Sarnowski
>[EMAIL PROTECTED]
>Penn Bioinformatics Core
>1316 Blockley Hall MC 6021
>(215) 746-7784
-------------------------------------
Brian Johnson
Systems Administrator
Work:  248.577.0383 ext 203
Cell:   906.281.0589
EMOL - Electronic Medical Office Logistics

Reply via email to