with nolock problem

Hi,
Is there a way to catch every select comming to sql and change it to
select with nolock?
or how to make database READ UNCOMMITTED permanent?
any ideas?
Richard

Rycho (sercik@interia.pl)  writes:
> Is there a way to catch every select comming to sql and change it to
> select with nolock?
> or how to make database READ UNCOMMITTED permanent?
> any ideas?

If there are no updates in the database, you can set it to READONLY, to
avoid the overhead of locking. But apart from that, there is no option to
do this on database level.

However, the application could issue SET TRANSACTION ISOLATION LEVEL
READ UNCOMMITED when it connects.

But I would definitely think twice before I took such a step. If you
have issues with blocking, maybe you should rather review indexing
than resorting to NOLOCK.



--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Thanks for your replay,
Richard

Hi,
Is there a way of using triggers for this?
Thanks,
Richard