This came across my twitter stream today: http://www.objectreference.net/post/NHibernate-and-Execution-Plans.aspx
The blog entry claims that prepare_sql = true really only solves the problem on a per connetion basis. Quoting the blog: "This seemed to fix the parameter size issue but now the queries were being sent using exec sp_prepexec which even had the DBA’s scratching their heads over as it’s documented as a system procedure used to facilitate cursors within SQL Server. The DBAs later informed us that running queries like this causes the execution plans to only be re- used per open connection so for every connection it would still have to create new execution plans." Here is the old thread on the issue: http://groups.google.com/group/nhusers/browse_thread/thread/7a0a341184796836/db3cb45cfc8f9a2b?lnk=gst&q=prepare_sql#db3cb45cfc8f9a2b I'm wondering what's the real deal with it. It seems like this "bug" is either not confirmed, in a state of limbo, or FUD/not real. Anyone know? It seems like it sould be a pretty big issue for a high volume app. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
