Hi all,
I have a few stored procedures which all perfom SELECT queries on a table in the database. Do these kind of stored procedures affect any other processes or procedures working on that table. I am talking about locks, blocks etc.
For example, the database has a table which gets updated periodically by some process which I don't know. Now I wrote some stored procedures just to do the SQL SELECT with some conditions in WHERE clause. Is there any possibility that my stored procedure failed and the because of this, the process that runs on the table was not executed?
No, SELECT statements don't cause any kind of locking.|||And if I don't talk about locking, can I be rest assured that there won't be anything else that can have an effect?
|||Selects are pretty unobtrusive. I can't think of anything you'd need to worry about.
|||
gt1329a:
No, SELECT statements don't cause any kind of locking.
If your isolation level is read committed, SELECTs do put a shared resource lock but it doesnt block any UPDATEs. Locking is different from Blocking. If reading to-the-minute committed data is not important you can explicitly use NOLOCK.
No comments:
Post a Comment