> From: "Mike yearwood" <[EMAIL PROTECTED]> > Dynamic SQL execution plans are cached! > > http://weblogs.asp.net/fbouma/archive/2003/11/18/38178.aspx
Yes and no. That cached value is a function of the true workload of the sever over then next x min. So yes it is and it will sort of remain in the cache, but as other work is getting requested it may have a very short shelf life. It also depends on what volume of ram and your settings for your procedure cache are. That being said, workers who repeat the same functionality may have their requests cached. But at what expense? We all know that you can't get something for nothing. Oh that second round trip to the server for each query will add up when your using client sided statements. This is a bigger issue that the comments bring up. Below goes into more details on this. http://www.sql-server-performance.com/stored_procedures.asp The reality of plan reuse is all a function of the data volumes in your tables. If your doing inserts in the hundreds to thousands per sec an sp will have to rebuild it's plan to adjust to the changing data. That is rare and your sp won't be worth much. But if your doing hundreds of inserts per min or per hour then it's great. You say tabs and I say spaces :-> _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
