SQL server 2000 -> JDBC Date Time Format Problem

M

mukesh bhakta

Hi guys,

We have a strange problem when Java talks to SQL Server 2000.

The following query runs great when executed from Query Analyzer.

SELECT prlc_plis_code, prlc_cust_id, prlc_startdate,
prlc_enddate, prlc_type FROM PriceListCustomer WHERE 1 = 1
AND prlc_cust_id = 'CU00001030' AND prlc_startdate < '15/07/2005
09:32:28 AM' AND prlc_type = 'A' ORDER BY prlc_startdate

But when executed through the Java code (using MS Jdbc:eek:dbc driver) we
get the following exception

<snip>
EXCEPTION - java.sql.SQLException: [Microsoft][ODBC SQL Server
Driver][SQL S
erver]The conversion of a char data type to a datetime data type
resulted in an
out-of-range datetime value.
at
sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6958)
at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7115)
at sun.jdbc.odbc.JdbcOdbc.SQLExecDirect(JdbcOdbc.java:3111)
at
sun.jdbc.odbc.JdbcOdbcStatement.execute(JdbcOdbcStatement.java:338)
at
sun.jdbc.odbc.JdbcOdbcStatement.executeQuery(JdbcOdbcStatement.java:2
53)
<snip>

The strange thing is it runs fine on our production server but has
problems on the dev server.

We have compared the db settings on both the machines using

select name ,alias, dateformat from syslanguages where langid =
(select value from master..sysconfigures where comment = 'default
language')

which yields

British British English dmy

This only tells me that there is some setting in Tomcat/JDBC which
needs attention.

Any tips would be of great help.

Cheers


MB
 
P

Paul Tomblin

In a previous article said:
AND prlc_cust_id = 'CU00001030' AND prlc_startdate < '15/07/2005
09:32:28 AM' AND prlc_type = 'A' ORDER BY prlc_startdate

But when executed through the Java code (using MS Jdbc:eek:dbc driver) we
get the following exception

<snip>
EXCEPTION - java.sql.SQLException: [Microsoft][ODBC SQL Server
Driver][SQL S
erver]The conversion of a char data type to a datetime data type
resulted in an
out-of-range datetime value.

Instead of trying to pass the timestamp as a character string, assign it
to a variable of type java.sql.Timestamp, and bind it.
 
M

mukesh bhakta

Hi Paul,

Thanks for the quick response.

However, the case being we do not want to change anything in the code
at the moment rather we want to take the existing production code base
and replicate a test environment.

Is there anything in the settings that we should check to confirm that
both servers are on the same wavelength?

Cheers

MB
 
Joined
Sep 5, 2006
Messages
1
Reaction score
0
I have the same problem. It works fine on one SQL Server instance but not on another. They both have the same langid etc... Did you have any success in solving this?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,768
Messages
2,569,574
Members
45,050
Latest member
AngelS122

Latest Threads

Top