Re: Access and equiv of Transact-SQL's Nolock hint?
From: Rick Brandt (rickbrandt2_at_hotmail.com)
Date: 07/08/04
- Next message: Brian: "Question for Duane Hookum"
- Previous message: AdmSteck: "Missing records"
- In reply to: MGFoster: "Re: Access and equiv of Transact-SQL's Nolock hint?"
- Next in thread: MGFoster: "Re: Access and equiv of Transact-SQL's Nolock hint?"
- Reply: MGFoster: "Re: Access and equiv of Transact-SQL's Nolock hint?"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 8 Jul 2004 13:29:53 -0500
"MGFoster" <me@privacy.com> wrote in message
news:RLfHc.9544$oD3.5181@newsread1.news.pas.earthlink.net...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Use pass-thru queries w/ the T-SQL NOLOCK hint.
>
> Don't you think that's kinda dangerous - reading an uncommitted
> transaction might result in invalid data returned in your query 'cuz an
> uncommitted transaction might be rolled back.
>
> Why don't you just test your queries in the SQL Query Analyzer & see
> what their times are, then set the Access query Timeout property to a
> little over that time?
Depends (as usual). I have had to use NOLOCK on a few occasions where I
was using a data table as the source of a ComboBox RowSource. Without
NOLOCK use of the ComboBox would impose a lock on the source table until
the last row of the list was accessed. Other users trying to make edits
against that table would then be blocked. Adding NOLOCK cured the problem.
-- I don't check the Email account attached to this message. Send instead to... RBrandt at Hunter dot com
- Next message: Brian: "Question for Duane Hookum"
- Previous message: AdmSteck: "Missing records"
- In reply to: MGFoster: "Re: Access and equiv of Transact-SQL's Nolock hint?"
- Next in thread: MGFoster: "Re: Access and equiv of Transact-SQL's Nolock hint?"
- Reply: MGFoster: "Re: Access and equiv of Transact-SQL's Nolock hint?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|