Update/Inserts and locking behavior tips/help needed
- From: oliviers <olivier.sanzot@xxxxxxxxx>
- Date: 23 Oct 2007 12:07:36 -0700
Hi,
I'm facing a problem when some users are uploading data to our SQL
2005 database.
A sp is creating a temp table. Data (a flat file) is just bulk loaded
into that temp table.
An update is then performed by executing an update statement which is
joining the main data table with the temp table.
My concern is that when some users are uploading their data (26000
rows), the whole DB seems locked.
Any other update is blocked, any other procedure call which is
performing updates is locked. Even some select statements are locked
while the mass upload is processed. Users can keep on working normally
as soon as that upload process is over.
What are the main locking parameters I should check in order to work
around that behavior?
I don't need real full locking as there is no real chance some other
users might update the data that is being uploaded.
Thanks,
Olivier
.
- Prev by Date: Re: Transferring Data Between SQL SERVERS (Express)
- Next by Date: How Create Job to Export->Access that Picks Up New Columns & Tables Without Re-Creating
- Previous by thread: parameterizing a view
- Next by thread: How Create Job to Export->Access that Picks Up New Columns & Tables Without Re-Creating
- Index(es):
Relevant Pages
|