select rows database lock?
From: gl (gl_at_discussions.microsoft.com)
Date: 02/25/05
- Next message: Sue Hoegemeier: "Re: select rows database lock?"
- Previous message: Aaron [SQL Server MVP]: "Re: SQL Send Mail Problem"
- Next in thread: Sue Hoegemeier: "Re: select rows database lock?"
- Reply: Sue Hoegemeier: "Re: select rows database lock?"
- Reply: David Gugick: "Re: select rows database lock?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 25 Feb 2005 05:47:02 -0800
When in the sql enterprise manager, if you right click a table and go to open
table--> select all rows, does that "lock" the database? As in if you select
all rows will someone else trying to read the data (via app or web interface)
and update it be locked out of it? We're often told that we shouldn't use
this method at our work and we should only run statements with nolocks on
live data. I had always thought that the data only locks when you put the
cursor in one of the rows to actually edit it.
What is the correct ruling? I could do tests myself but i'm not sure they
would be accurate. I mainly want to know what happens when you select all
rows (or select top) but don't put your cursor in the data.
- Next message: Sue Hoegemeier: "Re: select rows database lock?"
- Previous message: Aaron [SQL Server MVP]: "Re: SQL Send Mail Problem"
- Next in thread: Sue Hoegemeier: "Re: select rows database lock?"
- Reply: Sue Hoegemeier: "Re: select rows database lock?"
- Reply: David Gugick: "Re: select rows database lock?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|