SQL Kiwi (9/23/2012)

---

SQL Mad Rafi (9/23/2012)

---

is there a way that i can enfore it for that user from my side as a dba.

Not that I know of. There might be some way to enforce or distribute the setting using Windows policies - but that's not something I know much about.

Another solution you might consider is changing the database to use the read committed snapshot isolation level (ALTER DATABASE db-name SET READ_COMMITTED_SNAPSHOT ON). That way, readers at the default read committed isolation level will not take the shared locks that appear to be causing you a problem. There may be some impact on tempdb from enabling that option, more details in Books Online including the link below:

http://msdn.microsoft.com/en-us/library/ms189050.aspx