Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sqllearner
Aged Yak Warrior
639 Posts |
 Posted - 2006-02-24 : 01:17:41
|
| I took this specific paragraph from http://www.sql-server-performance.com/blocking.aspAvoid INSERTing, UPDATEing, or DELETEing large numbers of records in a single transaction. If you do, all the records affected by your action will be locked until the transaction is done. If you find that you need to perform mass data changes, it is better to batch them into smaller, shorter transactions to prevent unnecessary lockingIam actually in a confused state..Iam working in a project where we have to insert/update from staging to a prod database where there is a lot of individual stored procedure executed from a single stored procedure in a single transaction.Currently I have 2 options where there is a mass update or pass one emp_id to the main stored procedure and process each emp details using cursor..Currently its doing mass update in a single transaction.Iam scared of the single transation because it may cause blocking or locking..Is there any way we can avoid it....... |
|
|
sqllearner
Aged Yak Warrior
639 Posts |
Posted - 2006-02-24 : 01:43:14
|
| Here its outside the application.The job calls the Sp for inserting/updating.Please advise me... |
 |
|
|
sqllearner
Aged Yak Warrior
639 Posts |
Posted - 2006-02-24 : 12:05:57
|
| Please help me with this issue |
|
|
|
|
|
|
Single Transaction Issue