We're using NHibernate 1.2.1.4000 on a shared-tenant SaaS application. The database is our bottleneck, and we're trying to reduce the load on the database. One obvious question comes to mind: NHibernate seems to produce randomly generated column aliases. Are these queries going to be as scalable as stored procs? Will the database be able to cache them efficiently? I'm not a DBA, but I know one...

We're using SQL Server 2005 on Windows 2000 Server.

Thx!

Here's an example, perhaps that will help explain the problem:

NHibernate: SELECT top 5 this_.UserId as UserId2_0_, this_.ProjectId as ProjectId2_0_, this_.DisplayName as Display42_2_0_, this_.Password as Password2_0_, this_.EmailAddress as EmailAd44_2_0_, this_.StatusID as StatusID2_0_, this_.LastLoginDate as LastLog46_2_0_, this_.CreatedBy as CreatedBy2_0_, this_.CreatedDate as Created48_2_0_, this_.ModifiedBy as ModifiedBy2_0_, this_.ModifiedDate as Modifie50_2_0_, this_.OnlineVisibilityStatus as OnlineV51_2_0_, this_.OnlineActivity as OnlineA52_2_0_ FROM dbo.Users this_ WHERE this_.ProjectId = @p0 and this_.StatusID = @p1; @p0 = '11111111-1111-1111-1111-111111111111', @p1 = '1'

The items in bold change from one request to another. Does that prevent SQL Server from caching them as the same query? Our DBA says it does...