The BBDW refresh process does not use NOLOCK

It appears that the BB packages do not utilize nolock in queries to the source transactional database (CRM). For the purposes of loading a data warehouse that is basically a snapshot at a point in time, why wouldn’t it use dirty reads or NOLOCK?

Suggestions for changing the architecture of the software an be entered into our Ideas Portal.   The request documented in this article would best be covered in this Planned Idea to increase ETL reliability: https://bbcrm.ideas.aha.io/ideas/CRM-I-2302 

Steps to Duplicate

1) Turn on nolock for the session
2) Try to use NOLOCK while loading a data warehouse

Environment

 Blackbaud CRM
 4.0
 4.0.131.2

Was this article helpful?