NOLOCK

zeospike

Like a good boy, I always end a table selection in a SQL Server script with a (NOLOCK) to keep our DBA at bay.

I've noticed with version 4 adding (NOLOCK) causes the prompting to stop.

What I've also noticed though is that if I use WITH (NOLOCK) everything is fine.

So the moral of the story is, if you are lazy like me and can't be bothered to type the WITH, you're going to have to...unless like me you are really lazy in which case you've got it as a snippet.

Anu D

Thanks for your post regarding SQL Prompt.

This is a known issue and we have logged it in our tracking system and it will be definitely addressed in our future relase.
For your reference the id for the bug is SP-2225.

Sorry for the inconvenience caused by this issue.

nhustak

Extremly disappointed this was not fixed in latest release. This is causing me all kinds of problems as we use NOLOCK on a consistent basis and the databases I work with have a huge number of tables and fields. One of the MAJOR things it helps me with is my joins - which of course is broken with a (NOLOCK).

I have really come to rely on this product so you can imagine the impact of not having this work.