Our Hibernate application is working fine under MSDE (MSSQL desktop engine) using microsoft JDBC, however, it gives warnings when there is a new connection opened or closed like this:

13:26:37 WARN - SQL Warning: 0, SQLState:
13:26:37 WARN - [Microsoft][SQLServer 2000 Driver for JDBC]Database changed to <mydb>
13:26:37 WARN - SQL Warning: 0, SQLState:
13:26:37 WARN - [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Changed database context to '<mydb>'.
13:26:37 WARN - SQL Warning: 0, SQLState:
13:26:37 WARN - [Microsoft][SQLServer 2000 Driver for JDBC]Language changed to us_english
13:26:37 WARN - SQL Warning: 0, SQLState:
13:26:37 WARN - [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Changed language setting to us_english.

Although it does not cause trouble, it is quite annoying.
anybody familiar with this issue?

my connection url is:
jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=<mydb>;SelectMethod=Cursor;sendStringParametersAsUnicode=false

Hibernate version:
2.1.2

Are you using the standard hibernate connection pool? If so change it to another one ( C3P0 or proxol are the recommended ones ).

Plus don't use the Microsoft JDBC driver, it has many bugs and is quite slow compared to others.

See here

http://www.hibernate.org/80.html

Try the jTDS one, free and opensource.

I'm using Inetsoftware's Opta2000 driver and I'm receiving the same annoying warnings...

My guess is that you will probably receive these warnings regardless of the MSSQL JDBC driver in use.

Indeed, SQL Server returns these two messages on connect as warnings, so all JDBC drivers for SQL Server will return them (unless intentionally removed by the driver).

Alin Sinpalean,
The jTDS Project.

I found out that it appears that you can set a URL property "nowarnings=true" to disable the warnings using Inetsoftware's Opta2000 driver. Of course, that turns off all the warnings, but, I'm not sure how useful those warnings are anyway...

Well, that depends. You might want to know that the driver returned a forward-only read-only ResultSet instead of the scrollable updateabe you asked. The way to do that, according to the JDBC specification, is to call getWarnings() after you got the ResultSet and check the warnings. Or you could call setXXX() or previous() and get an SQLException. Your choice, really.

Alin,
The jTDS Project.