Nolock hints propagate through table and view hierarchy paths only. sccm reporting (2012 r2)utilizes the rbac model in reporting - all out of box reports use functions and nolock hints do not propagate functions. That is why no default reports use nolock hints. Unless the nolock is coded behind,in which case you would not know that anyway, unless you set up sqlprofiler.
If you build new reports via sccm console then this will be the same I think. If you build custom ssrs reports, then maybe you should use nolock, I don't know. I presume Microsoft will say, to do it in the console. Because the other, quite major, thing about building custom ssrs reports is, how do you implement the rbac? From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: 02 March 2015 16:23 To: [email protected] Subject: RE: [mssms] Nolock on reports. Never heard of it, have written hundreds of reports and no issues I am aware of. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Robert Spinelli Sent: Monday, March 02, 2015 9:29 AM To: mssms Subject: [mssms] Nolock on reports. Having an internal debate in regards to writing reports for SCCM 2012 using / not using nolock. Just wondering what others do? Do you use nolock when writing queries/reports? I've never used nolock, but others who are much better here at SQL said nolock should always be used. They were surprised when I pointed out that none of the built in SCCM reports using nolock. Thanks Rob The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
