<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results matching tags 'Error Handling' and 'indexed views'</title><link>http://sqlblog.com/search/SearchResults.aspx?o=DateDescending&amp;tag=Error+Handling,indexed+views&amp;orTags=0</link><description>Search results matching tags 'Error Handling' and 'indexed views'</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>Connect Digest : 2009-10-30</title><link>http://sqlblog.com/blogs/aaron_bertrand/archive/2009/10/30/connect-digest-2009-10-30.aspx</link><pubDate>Fri, 30 Oct 2009 15:50:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:18245</guid><dc:creator>AaronBertrand</dc:creator><description>&lt;p&gt;Light helping this week.&amp;nbsp; I am busy closing out a few projects (or at least chapters within projects) in preparation for PASS next week.&lt;/p&gt;&lt;p&gt;&lt;br&gt;========================================&lt;br&gt;

&lt;br&gt;
&lt;a href="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=506453" title="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=506453" target="_blank"&gt;#506453 : Lock escalation no longer kicks in for INSERTs in SQL Server 2008&lt;/a&gt; &lt;/p&gt;&lt;p&gt;Adam
found a nasty lock escalation bug in SQL Server 2008.&amp;nbsp; This one is
actually serious enough that it has me really hesitant about my plans
for moving to the new version in production, as we process a lot of data in bulk operations like this (loading millions of rows into staging tables, then inserting/updating existing tables). &lt;br&gt;&lt;br&gt;&lt;/p&gt;
&lt;p&gt;========================================&lt;br&gt;&lt;br&gt;&lt;a href="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=503207" title="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=503207" target="_blank"&gt;#503207 : Bad query plan leads to wrong results (incorrectly uses indexed view)&lt;/a&gt; &lt;/p&gt;&lt;p&gt;In this one there is an indexed view matching problem which can produce incorrect results.&amp;nbsp; The fix is in SP1 CU1, so this isn't a "go vote for this issue" mention, but rather encouragement to get up to SP1 + the latest CU (which was &lt;a href="http://support.microsoft.com/default.aspx/kb/973602" title="http://support.microsoft.com/default.aspx/kb/973602" target="_blank"&gt;Cumulative Update 4&lt;/a&gt; at the time of writing) if you're currently sitting at SP1 or lower.&lt;/p&gt;&lt;p&gt;&lt;br&gt;
========================================&lt;br&gt;
&lt;br&gt;&lt;a href="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=504631" title="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=504631" target="_blank"&gt;#504631 : add RAISE syntax for propagating exceptions&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=127228" title="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=127228" target="_blank"&gt;#127228 : Rethrow last error&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=125719" title="http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=125719" target="_blank"&gt;#125719 : Support Reraising Of Original Error In Catch In T-SQL&lt;/a&gt;&lt;/p&gt;&lt;p&gt;A lot of people want RERAISE() and/or RETHROW() among other enhancements to error
handling.&amp;nbsp; They are definitely looking at these changes for future
versions of SQL Server, so have your opinion heard!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item></channel></rss>