I'm thinking it's some configuration issue. When viewing the query executing in sql profiler, the query as executed by nhibernate uses 100x more cpu and I/O than the same query as executed by either management studio or a basic ado.net call. Is there a configuration option that could cause this?
On Tue, May 4, 2010 at 3:39 PM, Alan N <[email protected]> wrote: > I've got a named query that's not complicated, a few joins, returning > a row count. This query when executed by NHibernate is taking around > 50 seconds to complete as measured in sql profiler and nhprof. When I > copy the the query from profiler and execute it with a simple ado.net > call (or in sql management studio) it executes in around a second. > > Has anyone experienced this before? Have any insight? -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
