I am trying to better understand which DDL actions are possible to execute using a SQL Server DBA Account against feature classes registered with the geodabase in ArcGIS 10.2. This DBA Account is not the schema owner or the assigned SDE account. In our company, all DDL statements are supposed to be executed by the DBA group via sql scripts created specifically for deployment purposes. We are not allowed to use ArcMap or any other ArcGIS tools. The problem is that we have tried to execute alter statements before using TSQL instead of ArcPy/Python and we have seen weird issues with SDE not understanding the change. Somehow the internal SDE catalog gets out of sync and it either things the field has not been modified or it thinks the feature class still exists even thought it was deleted using a 'DROP' statement. Any ideas on how to manage changes and maintaining a geodatabase in a company with strict separation of duties policies? Appreciate your feedback.