I am using the hibernate tools version 4.0a. I am trying to connect to a SQL Server 2000 database. I can connect to the database no problem but when I run the reverse engineering tools to generate POJOs and Mapping files it produces no output, just a single file named GneralHbmSetting.hbm.xml that is empty.

Below is a copy of my configuration file:

<hibernate-configuration>
<session-factory>
<property name="hibernate.default_schema">ORDER_LOG</property>
<property name="hibernate.connection.username">SA</property>
<property name="hibernate.connection.password">SA</property>
<property name="hibernate.dialect">org.hibernate.dialect.SQLServerDialect</property>
<property name="hibernate.connection.url">jdbc:microsoft:sqlserver://localhost:1433</property>
<property name="hibernate.connection.driver_class">com.microsoft.jdbc.sqlserver.SQLServerDriver</property>
</session-factory>
</hibernate-configuration>

I know that this issue has been raised by others in connection with oracle and the soluation was to make the username, password and default schema capital letters but that doesn't seem to work with SQL Server. Any help would be most appreciated.

does your user have the proper rights to read the schema ?

Yeah, I user has access to everything in that schema. This is really stumping me. I used the hibernate tools on a MySQL database without any trouble but can't get it to work with SQL Server at all.

Use jTDS jdbc driver. Works like a charm.

In the past with the microsoft driver I have to include the schema and catalog as well to get it to work. Anyway, I only use jTDS now and how had no issues getting it to connect to MSSQL.

That worked like a charm. David you are a lifesaver. I would have thought that Microsoft knew how to write a good JDBC driver for their own database but I guess not. jTDS is definitely the way to go.

Thanks - Microsoft JDBC has not been all that good in the past I understand they have a new release that is much improved - I would not bother. jTDS is a fine product and works very well.

David,

Actually the new Microsoft driver is an OEM-ed version of the JNetDirect driver so it should be much better than the old DataDirect derived one. However in my testing I found literally tens of bugs so they still have a long way to go (if they want to do it in the first place).

Alin,
The jTDS Project.

Thanks for the detailed clarification.