Most database developers have been told at some point that using the NOLOCK hint is dangerous ... and yet many source control repositories are stuffed to the gills with NOLOCK. Why? Most likely because blocking is a real problem and NOLOCK does often help reduce blocking. If we accept that NOLOCK is bad then what strategies should be used instead to reduce blocking? It can be extremely difficult (impossible?) to find a DBA that is excited about supporting LINQ to Entities (or other object relational mapper) workloads. And yet LINQ is still pretty frequently used. Why? Most likely because non-ORM alternatives such as ADO.Net are a lot more work for the developers. Is this a hopeless conflict, or can deloper teams do things to make DBA lives less painful when using LINQ? If you’ve ever been frustrated by the feeling you’re told what not to do, without positive guidance on alternatives, this half day session may be for you.

(Lunch is NOT provided for Half-Day Pre-Con Attendees)

with Rick Lowe