Microsoft SQL Server 2000 JDBC Driver issue

I was wondering if anybody has run into the following problem with ms's
jdbc driver. We're using cursors in our app - when we create a
java.sql.Statement object in the app, we're indicating that we want the
corresponding ResultSet object to have a TYPE_FORWARD_ONLY cursor.
We've noticed when we do this that if the app executes a query with
'UNION's in it, it never gets a ResultSet back from the server (I've
noticed on the SQL server profiler that it stays stuck doing the 'exec
sp_cursoropen' call). If we change the resultSetType to
TYPE_SCROLL_INSENSITIVE then the query returns in no time.
Any ideas?
Thanks.
--Yogesh
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
joe wrote:

> I was wondering if anybody has run into the following problem with ms's
> jdbc driver. We're using cursors in our app - when we create a
> java.sql.Statement object in the app, we're indicating that we want the
> corresponding ResultSet object to have a TYPE_FORWARD_ONLY cursor.
> We've noticed when we do this that if the app executes a query with
> 'UNION's in it, it never gets a ResultSet back from the server (I've
> noticed on the SQL server profiler that it stays stuck doing the 'exec
> sp_cursoropen' call). If we change the resultSetType to
> TYPE_SCROLL_INSENSITIVE then the query returns in no time.
If you can show an example of your code, it'll help.
If you do a trivial query like "select * from sysdatabases UNION select * from sysdatabases"
that hangs?
thanks
Joe

> Any ideas?
> Thanks.
> --Yogesh
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
sql

Microsoft Please help-Web Service Problem

We had an app that called across to the web services to run batches of statements. Everything worked fine and now they stopped working. The report can still be ran from report manager. What things do we need to check to find the problem? Any help would be greatly appreciated.

Try turning on tracing and view the logs. Also see event viewer if there are any issues. It could be an issue with the app or connectivity instead of Reporting Services, since the web service is used to service Report Manager.

More info on logging.

http://msdn2.microsoft.com/en-us/library/ms156500.aspx

cheers,

Andrew

|||Thank you Andrew for your prompt response. We will look at the logs and see if that leads us in the right direction.|||

Some security patches were applied to the server in December. Is it possible that these could have messed with the way that authentication is handled?

Patches:

KB925398

KB925454

KB923689

KB911897

KB926247

KB923694

|||The app is getting the message back "The report server cannot open a connection to the report server database. A conection to the database is required for all requests and processing. SQL server does not exist or acess denied."|||Is it possible that any of these security patches could have messed with our authentication? Any suggestions Please.