Hibernate Layer - 05-08-2007 , 04:41 PM
Does any one have any experience with the Hibernate layer [which acts as an
abstraction layer between DB & application layers]? The factor which is
bothering me is the absence of stored procedures. All transactions are done
via this Hibernate. What I am looking at is a system which does not use any
stored procedures at all. This will prevent the db server from using\reusing
a compiled execution plan coupled with all good stuff such as distribution
The other way to look at is that the sql queries generated & submitted to
the db engine from Hibernate layer will force the query optimizer to do its
work and create an execution plan and cache it in procedure cache [do not
know if they can use a sp_executesql in Hibernate layer…]
I assume that this will introduce a lot of load on the db system for
read\write operations. The folks are already noticing some issues at the
locking\blocking areas with this infrastructure. The real locking\blocking
effects are yet to be seen!
Any thoughts\comments are greatly appreciated.
Senior SQL DBA
Re: Hibernate Layer - 07-25-2007 , 04:50 AM
I not have direct experience with Hibernate but I recall that NHibernate
(the .NET version) has recently added stored proc support. NHibernate
follow Hibernate (Java version) evolutions. Try find informations on Web.
MCP Sql Server 2000 Ent.Ed.