2005 introduces the snapshot isolation level (their name for their MVCC implementation). 2000 and earlier were plagued by deadlock issues. I do not know of an easy way around that besides "protecting" those tests individually via the "skipping" mechanism. I do not have the time to do that right now. And honestly, I don't care about SQLServer pre-2005... So if you can run against 2005, great, lets do that; if not, lets just leave this one be for now. jTDS (at least when I last tried) will not work with SQLServer 2005 for a couple of reasons (for example, jTDS bombs when you try to set 4096 as the isolation level). It has been about a year now, so this may have changed. -----Original Message----- From: Aleksandar Kostadinov [mailto:akostadinov@jboss.org] Sent: Tuesday, December 05, 2006 2:50 PM To: Steve Ebersole Cc: hibernate-dev(a)lists.jboss.org Subject: Re: [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors] jtds guys say their driver is recommended for hibernate ;) Only this one hangs. It's not a problem to use the MS jdbc driver but is it necessary to run on 2005. We now have only 2000. Steve Ebersole wrote: there consider