﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / T-SQL (SS2K8)  / HOLDLOCK along with UPDLOCK / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 19 Jun 2013 20:54:48 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: HOLDLOCK along with UPDLOCK</title><link>http://www.sqlservercentral.com/Forums/Topic1405553-392-1.aspx</link><description>The update lock is held until the transaction commits or rolls back.</description><pubDate>Thu, 10 Jan 2013 11:53:06 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>HOLDLOCK along with UPDLOCK</title><link>http://www.sqlservercentral.com/Forums/Topic1405553-392-1.aspx</link><description>Hi,Using either HOLDLOCK or UPDLOCK as a lock hint allows other transactions to see the data, but, when used together, the other transactions cannot see the data until the previous transaction is completed.Can anyone shed some light on what happens when these locks are used together, and what happens. Thanks.</description><pubDate>Thu, 10 Jan 2013 10:32:05 GMT</pubDate><dc:creator>mymail.default</dc:creator></item></channel></rss>