I work for a State government, and we commonly store GIS data in SQL server geodatabases. Our typical workflow is to assign databases by agency. This means multiple agencies can have databases on the same SQL server, but they can't access each other's data. A problem we constantly run into is with breaking locks. We have popular datasets that might be viewed by hundreds of people at a time. Even just viewing a dataset creates a lock that doesn't allow any schema changes to be made (e.g., adding and deleting fields, enabling archiving, versioning, etc.). Currently, to break locks in a SQL database from ArcGIS Pro you have to have the processadmin server role. The problem with this is that it is a SQL server-wide role. Our IT database administrators DO NOT want to give this role out to agency users. So power users at our agencies are constantly frustrated that they can't make some of these needed changes to their data very easily. I propose removing the requirement to drop connections in order to break locks. @ColinZwicker
