nHibernate performanc testing?

liang · **Joined:** Wed Dec 07, 2005 1:33 am **Posts:** 7

I am using nHibernate in my current project, not too big, around 20 tables I love it. It is so great that my development work is becoming boring now. :D
But I do have a question here. Our DBA always claims that dynamic sql is bad. nhibernate probably only work for smaoll project, otherwise there will have performance issues. He can not check index in where clause, and so on. I think probably most of you have already faced before. Could anybody give me any hint how to make them believe the values? How can I do a performance testing, comparing with ADO.NET+stored procedure. How many overhead it will be? I am not a database guy, not very clear how dynamic sql or stored procedures work internal database (SQL Server 2000). But I guess the most overhead will come from reflection.

Very appreciate for any suggestion.

KPixel · **Posted:** Mon Dec 19, 2005 7:56 am

May be this topic has some useful information for you: NHibernate performance.

radu · **Joined:** Wed Jun 15, 2005 4:17 am **Posts:** 156

Well, there are a lot of debates about dynamic SQL vs Stored Procedures - google for them. The issue here is that your DBA has a narrow perspective. The gain in using an ORM comes from the time saved in development (which is paid later with a slight runtime overhead). Anyway computer time is very cheap compared with the programmer time! If your DBA is worried about security, if you use parameterized queries, NH should use parameters as well (I think the NH team will aprove me). Also there are some posts which explain how to use stored procedures with NH.

HTH,
Radu