SQL 2000 – SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED

SQL 2000 – SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED

We are about to launch a web site. To speed up response time, we are thinking of adding SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED in our stored procedures.

There is an understanding that this may transient 605 error messages. (e.g. When a query using NOLOCK or READ UNCOMMITTED attempts to read data that is in the process of being moved or altered by another user, a 605 error occurs.) Microsoft SQL Server 2000 has a service pack that contains this hotfix.

Does anyone have any positive or negative experience in
1)using SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
or
2)using the above after applying the Microsoft hotfix

Thank you,
Kathy