Is the NOLOCK (Sql Server hint) bad practice?
问题 I\'m in the business of making website and applications that are not mission critical -> eg. banking software, space flight, intensive care monitoring application, etc. You get the idea. So, with that massive disclaimer, is it bad using the NOLOCK hint in some Sql statement? A number of years ago, it was suggested by a fellow Sql Administrator that I should use NOLOCK if I\'m happy with a \"dirty read\" which will give me a bit more performance out of my system because each read doesn\'t lock