3 replies to this topic

[Marlon]

With PROIV v9, PROIV in their wisdom removed the insertion of WITH (NOLOCK) into SQL produced from SQL ENDSQL blocks in logic so whereas this SQL SELECT column1, column2 FROM table1 ENDSQL would have produced this actual SQL SELECT column1, column2 FROM table1 WITH (NOLOCK), up to and including 9.54.9 it just made this SELECT column1, column2 FROM table1 so of course there's a fair chance you'll get a barrel load of locking problems. Not only did they do this with no prior warning, so at least you'd have some time to amend your code, they also did it with no notification in the release notes. Fortunately, someone has realised what an almight c!ck-up this is and it's supposedly being reversed in a release due very soon after me writing this on 30th March, 2021.

[Richard Bassett]

As a matter of interest, would you be experiencing locking issues here because you are not using row versioning?

 

(IIRC, row versioning a.k.a. MVCC is an optional thing in SQL/Server, unlike Oracle, Postgres and MySQL/InnoDB)

[Marlon]

As a matter of interest, would you be experiencing locking issues here because you are not using row versioning?

 

(IIRC, row versioning a.k.a. MVCC is an optional thing in SQL/Server, unlike Oracle, Postgres and MySQL/InnoDB)

Interesting question.  I'll ask the customer what they're doing.  However, as PROIV have made no mention of this and have said they're putting back the auto-insert of WITH (NOLOCK), I suspect it's not relevant.

[Marlon]

v9.61 is now out on the PROIV website which, PROIV say, fixes the WITH (NOLOCK) issue.