Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Table Locking caused by Update
Message
De
07/06/2002 08:52:24
 
 
À
06/06/2002 19:23:09
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Autre
Divers
Thread ID:
00665741
Message ID:
00665891
Vues:
21
SQL Server is putting a Table lock on table A? SQL Server is biased towards row locks.

Technically, you can prevent SQL Server from using locks. You could set the Transaction Isolation Level to Read Uncommitted. THIS IS NOT RECOMMENDED!!! I think you would be better served by determing the reason why a Table lock is being issued.

Do you have an applicable index for finding the row in Table A? Try using sp_lock to determine how many and the kind of locks that are being applied to Table A.

Can you provide more information? Maybe a subset of the source?

-Mike


>I am using the folowing code
>1 dbsetprop transactions to manual
>2 read a record from table A
>3 then insert a record to table B or table C
>4 then update table A that the record has been processed
> and where the data was inserted
>5 then commit
>Between steps 1 and 5 the table A is locked
>This prevents other programs from inseritng into table A
>Is there any way to prevent the locking.
>TIA
>Noach
Michael Levy
MCSD, MCDBA
ma_levy@hotmail.com
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform