http://sqlblog.com/blogs/alexander_kuznetsov/archive/tags/query+performance/indexed+view/default.aspxTags: query performance, indexed viewenCommunityServer 2.1 SP2 (Build: 61129.1)http://sqlblog.com/blogs/alexander_kuznetsov/archive/2009/06/02/be-ready-to-drop-your-indexed-view.aspxTue, 02 Jun 2009 21:10:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:14419Alexander Kuznetsov10http://sqlblog.com/blogs/alexander_kuznetsov/comments/14419.aspxhttp://sqlblog.com/blogs/alexander_kuznetsov/commentrss.aspx?PostID=14419In all-too-many cases an indexed view may solve your short term performance goals but at some later time become counterproductive. So if you choose to use an indexed view, you may need an exit strategy. Let me describe a few common problems with indexed...(<a href="http://sqlblog.com/blogs/alexander_kuznetsov/archive/2009/06/02/be-ready-to-drop-your-indexed-view.aspx">read more</a>)<img src="http://sqlblog.com/aggbug.aspx?PostID=14419" width="1" height="1">Transact SQLDeadlocksquery performancelock contentionindexed view