DLA, who had hired my company to redress the issues of Deadlock, had told me only that if we set up the transaction, our olt database locking problems will be improved. Read the level from the United Nations to read the level.
Is not it just 100% false? Read more:
More information:
Our data is very "silenced" and user-specific. 99.9999999% of all user interactions work with our data and our dirty reading scenarios, if they are, what the user can try to do.
Thank you for all the answers, DBA became useless in the question, and we fixed the issues of locking by adding an index.
I am sorry that I have not specified that the locked problem was being made for the update statement and there is no regular selection. While dealing with locking issues, different solutions have been given to two different query types.
It is like sound, part of a grain decision, though without all the details of your environment It's hard to say.
You should advise your DBA to consider using the advanced segregation facilities of SQL Server, i.e. row versioning technology It was introduced in SQL Server 2005 so that problems can be addressed specifically with the OLTP database which experiences high lockout.
The following white paper has a lot of complex topics but it is necessary for all exceptional DBA to be read. This includes an example of using additional isolation levels in different types of environments such as the OLTP, Offloaded Reporting Environment etc. In essence it will be both stupid and greed.
I hope this helps, but please tell me if you need more then please modify transaction segregation for all your T-SQL queries, without developing a solid understanding of it. the explanation.
Cheers!