从SET TRANSACTION ISOLATION LEVEL (Transact-SQL)开始：

READ COMMITTED

Specifies that statements cannot read
data that has been modified but not
committed by other transactions. This
prevents dirty reads. Data can be
changed by other transactions between
individual statements within the
current transaction,resulting in
nonrepeatable reads or phantom data.
This option is the sql Server default.

The behavior of READ COMMITTED depends
on the setting of the
READ_COMMITTED_SNAPSHOT database
option:

• If READ_COMMITTED_SNAPSHOT is set to OFF (the default),the Database Engine
  uses shared locks to prevent other
  transactions from modifying rows while
  the current transaction is running a
  read operation. The shared locks also
  block the statement from reading rows
  modified by other transactions until
  the other transaction is completed.
  The shared lock type determines when
  it will be released. Row locks are
  released before the next row is
  processed. Page locks are released
  when the next page is read,and table
  locks are released when the statement
  finishes.
• If READ_COMMITTED_SNAPSHOT is set to ON,the Database Engine uses row
  versioning to present each statement
  with a transactionally consistent
  snapshot of the data as it existed at
  the start of the statement. Locks are
  not used to protect the data from
  updates by other transactions.

When the READ_COMMITTED_SNAPSHOT
database option is ON,you can use the
READCOMMITTEDLOCK table hint to
request shared locking instead of row
versioning for individual statements
in transactions running at the READ
COMMITTED isolation level.

(重点补充)

更改数据库配置以将READ_COMMITTED_SNAPSHOT变为ON.

此外,尽量保持您的事务尽可能短,并确保您在后台进程中提交事务(每小时执行10,000次插入),因为如果它从未提交,则选择将永久阻止(在默认设置下).