Win a copy of Head First Android this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Rob Spoor
  • Devaka Cooray
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Tim Holloway
Bartenders:
  • Jj Roberts
  • Al Hobbs
  • Piet Souris

I am facing a lot of problems with sql server 2000 odbc drivers.

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi all.....
I am facing a lot of problems with sql server 2000 odbc drivers.
and the database

when i try a awt database application in ms access it is working perceftly

but is it not working in using sql server 2000 database and i am using the JRUN 4 as the java server

and some times i am getting the exception with sql server

java.sql.SQLException : [Microsoft] [ODBC SQL Server Driver] Connection is busy with results for another hstmt.


pl give me some solution to my problem

i am facing pblm from past 2 weeks

pl give me replies at suhavchaudhary@yahoo.com

thank you
suhav
 
author & internet detective
Posts: 40795
828
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Suhav,
Welcome to JavaRanch!

Are you using connection pooling or threads? Are you closing your result sets, statements and connections? Is it possible that the connection is in use?
 
tumbleweed and gunslinger
Posts: 192
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It sounds like you are not properly closing your connections, statements, or something like that.

We're using SQL Server 2000 and process over 100 million DB operations a month with no issues.

One word of caution, eventhough many people say you do not have to close Statements, PreparedStatements, or CallabelStatements before closing Connections: do it. It does matter. Don't leave it up to the driver to handle this. We've found vast differences in how drivers handle this, especially the MS Type 3 Driver, which is aweful BTW.
[ November 04, 2004: Message edited by: David Yutzy ]
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic