Hi everyone, Short problem description: We have created Spring web application using Hibernate and working with Oracle 9i database (with Spring support for Hibernate mapping). Everything works great, performance is very high ( database read and write operations times are very short ). Our problems began when we tried to adapt our application to work with Sql Server 2000 database. Theoretically, we had to do only a few modifications in our application code (changing some Hibernate mapping files). From the functionality point of view application works just like with Oracle 9i database but the performance has decreased 10 times !! We loged execution times of every main operation using Spring Interceptor class. Sequence of writing and reading 3 groups of objects (3 Hibernate flush and 3 refresh operations ) take 3 seconds for Sql Server 2000 databse while the same operations for Oracle 9i take 300 ms ! Some info about software that we use: 1. Spring ver. 1.2.3 2. Hibernate ver. 3.0.5 3. JDBC drivers for Sql Server: We tried many drivers (list below) but in every case there was no performance improvement: - INET Merlia TDS - jTDS (sourceforge.net) 1.1 i 1.2 - Microsoft driver for MS Sql Server 2000, - Microsoft driver for MS Sql Server 2005 beta 1, beta 2 4. DataSource and pooling We use our own DataSource and Pooling class implementations ( we tried also Microsoft solutions but it didn't change anything ). Based on performed tests we rejected following issues as cause of performance problem: 1. Implementation of Sql Server 2000 - in generall Sql Server is faster then Oracle; we analysed sql statements execution times using Sql Profiler. Execution times were short but there were "time gaps" between each statement execution. 2. JDBC driver - we tested many drivers, many driver parameters combinations but the performance wasn't changing at all. We suspect that there could be also a general problem connected with the locking features of the SQL Server database. I've heard that in SQL Server 2005 there is a new mechanism for that - is there a chance that our application will be running faster on 2005? We suspect also that JDBC itself can be the cause - we've made a comparison using .NET and JDBC. We have done it with 22 consecutive select statements. It took about 30 ms in .Net and about 200 ms with JDBC. About our database - it contains very few data and the select statements we have problems with are based on ID values so it's rather not the case of indexes/etc. (we suppose so). We know that it is hard to figure out problem solution based on our summary information but we hope that somebody encountered already the same problem. Thanks in advance for any ideas.