Hi
This is not something you would want do as a default, and when you do
require it, then it has to be a concious decission to allow this;
therefore not having it at server level or as a default for the
connection is probably a good thing. You can always set it for the
connection/session.
John
se*******@hotmail.com (neo) wrote in message news:<15*************************@posting.google.c om>...
Thanks to Dan/John.
No I just wanted to allow dirty-read, not read-only db.
I thought there was an option in SQL to set db to allow read uncommited.
Maybe for SQL 7?
"John Bell" <jb************@hotmail.com> wrote in message news:<bo**********@titan.btinternet.com>... Hi
To add to Dan's comment...
Are you wanting to make the database read only?
John
"neo" <se*******@hotmail.com> wrote in message
news:15**************************@posting.google.c om... I'm having problem with locking in update and select.
my update takes long and select from clients happens all the time.
I know with NOLOCK in select or set transaction isolation level, I can
read data uncommited.
I want to know if there is an option I can change on server or
database
to change isolation level for all incoming connections.
thanks for your help in advance.