Sean Lange (7/25/2014)
SQLRNNR (7/25/2014)
Sean Lange (7/25/2014)
WOW!!! If you have ever wondered about the quality of responses at SO just checkout this response to a question about when it is appropriate to use NOLOCK.Most banking applications can safely use nolock because they are transactional in the business sense. You only write new rows, you never update them.
From what I am hearing by some people, a lot of Banks use BASE rather than ACID. In BASE, nolock would be ok because they write new rows 15 or 16 times or something like that.
I wonder how these systems deal with credit card transaction requests. Would be interesting to see how this gets used.
The numerous writes allows them to take the values from the majority of the writes and persist that. If the values are different a couple of times, that is ok because they toss out the "bad" rows. Different approach and I suppose it could work.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events