June 30, 2008 at 7:59 am
Hey guys,
You think you have problems now? Wait until nHibernate and all it's ilk are in your development systems. Now you'll have object specific databases with dynamic SQL. Tuning headaches just got bigger.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 30, 2008 at 8:02 am
Grant Fritchey (6/30/2008)
Hey guys,You think you have problems now? Wait until nHibernate and all it's ilk are in your development systems. Now you'll have object specific databases with dynamic SQL. Tuning headaches just got bigger.
You're telling me!! nHibernate was all new to me when I joined this place and boy does it make life tough at times!
June 30, 2008 at 4:39 pm
We get nHibernate errors here every day (he said with his head in the sand)
July 1, 2008 at 5:26 am
Really? You're using it? Any words of wisdom on either living with it well or avoiding it entirely?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 1, 2008 at 5:29 am
I generally hide under the desk and pretend it doesn't actually exist :w00t:
July 1, 2008 at 5:32 am
We've got some development teams advocating for it's use right now. I'm trying to build a strong case on either a correct usage (and that DOES NOT mean object databases) or no usage at all. For this supposedly being the wave of the future, documentation on implementation, past medium to small web apps, is pretty darned light.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply