Doug Baroter (qwert12345 (AT) boxfrog (DOT) com) writes:
This has nothing to do with JDBC. What is happening is that when
you run the command from JDBC, one or more of @col1, @col2 and @col3
are never assigned any value, yield in correct SQL.

A tip is that when you generate dynamic SQL, to always include a debug
path that printes the SQL string.

Since you say that it works in QA, my guess is that he JDBC thing
does not execute in the same database as you run it from QA.

And why you have a hardcoded object id is beyond me...

--
Erland Sommarskog, SQL Server MVP, sommar (AT) algonet (DOT) se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

Doug Baroter (qwert12345 (AT) boxfrog (DOT) com) writes:
Does that object still live?

I should probably have emphasized that the last bracket in the message
makes it clear that it comes from SQL Server.

[Macromedia][SQLServer JDBC Driver][SQLServer]
Incorrect syntax near the keyword 'as'.

Thus, the likelihood that the JDBC driver is the culprit is small. That
would imply that the JDBC driver mangles the batch somehow. And it
certainly has nothing to do with JDBC driver not supporting column
aliases.

Exactly how does the Java code that emits this SQL look like? From
where do you get the object ID?

If you have admin priviledges on SQL Server, you can use the Profiler
to see what actually is sent to SQL Server.

--
Erland Sommarskog, SQL Server MVP, sommar (AT) algonet (DOT) se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp