Hi all,

I've been working with nhibernate for a while now and I'm pleased to see it working with stored procedures since it allows me to use it under circumstances where clients will refuse it's use due to the lack of stored procedure support of previous versions.
I don't know if this is actually a help request or if it's more a heads up about a situation that I've comme up to after profiling with a dba nhibernate's execution scripts.
I'm using version 1.2.0 with SQL Server 2000 in a high performance enviroment. Nhibernate executes the required stored procedures through parameterized queries by executing sp_executesql. Now the problem is that this way of calling the procedure will cause the querry to be compiled and cached everytime it's issued with different paramaters. The following LinQ post (it is having the same problem) will certainly explain better than I what is happening with this way of executing the stored procedures.

http://rocksthoughts.com/blog/archive/2 ... ckups.aspx

Now, is there a way of forcing the parameters to be passed with a fixed length as defined in the mapping file? Getting explicit stored procedure calls would be even nicer, but I haven't read about it in any post nor blog.

Thanks!