Chris,
Have you checked the server logs for a specific error?
I had a similar problem related to the length of the query string
with a MYSQL database, which returned the error message "Got a packet
bigger than 'max_allowed_packet' ".
I have forgotten if MSSQL has a similar setting.
Paul
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
--
Sincerely,
Paul Appleby
(416) 530-0070
http://www.paulappleby.com
http://myspider.ca
