The UR(uncommited read) isolation level provides read-through locks, also know as dirty read or read uncommitted. Using UR can help to overcome concurrency problems. When you're using an uncommitted read, an application program can read data that has been changed but is not yet committed.
UR can be a performance booster, too, because application programs bound using the UR isolation level will read data without taking locks. This way, the application program can read data contained in the table as it is being manipulated.
For ex: Suppose a user updates a data(changes name from Sam to Samuel) and it`s yet not commited.And now a second user tries to access that data.With UR(Uncommited Read) the second user will get the updated data(i.e sameul) even though the changes done have not been commited into the database. So UR is a real relief for projects which involve quick updation and read like yours.