>>>With NOLOCK is a SQL Server option.
>>>
>>>Open Help in SQL Server, Search and type "dirty reads".
>>
>>Ok, I have found that this is related to the SET TRANSACTION ISOLATION LEVEL setting. How can I know the current setting of that setup?
>
>Great question! I scanned through BOL quickly but don't see an answer. I googled it, but no answer either. I didn't find it in SSMS yet either.
>
>In the meantime I found this artricle
>http://emea.windowsitpro.com/emea/article/articleid/92780/sql-server-2005-transaction-isolation-levels----how-to-handle-data-concurrency-through-versioning.html
>
>which is probably not that relevant, I haven't yet read it in full.

See this topic in BOL
"Adjusting Transaction Isolation Levels". So it looks like you can set it in SQL Server only through T-SQL (no option in SSMS) or you can set it from ADO.NET It doesn't say if you can get it from there, but perhaps you can try.