The article about change and configuration management is very good. However, I dhttps://community.appian.com/discussions/f/process/404/the-article-about-change-and-configuration-management-is-very-good-however-i-dThe article about change and configuration management is very good. However, I don&#39;t understand one point that is being made at the &quot;Database Change Management Best Practices&quot;( forum.appian.com/.../Change_and_Configuration_Management The fourth pointen-USTelligent Community 12RE: The article about change and configuration management is very good. However, I dhttps://community.appian.com/thread/1183?ContentTypeID=1Thu, 17 Jan 2013 23:11:25 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:0e225f57-947c-4dcb-a643-74fb760e83d4Mike CichyWhat it means is that the DB changes that are related to each other should be implemented together, rather than piecemeal. For example, you cannot add a column that references a PK in a table that has not been created yet.<div style="clear:both;"></div>