I'm getting charged per GB for SQL Server storage, so I have an incentive to use just as much storage as I need and no more. There are enough GB involved to create an attractive benefit to using less storage. I immediately think, "shrink the database." Then I think, "uh oh."
I notice that the Esri help is silent on the subject:
- ArcGIS Pro: Enterprise geodatabase maintenance tasks—Manage geodatabases in SQL Server | Documentation
- ArcMap: Geodatabase maintenance—Help | ArcGIS Desktop
While the Microsoft help is not:
- SQL Server 2016: Shrink a Database - SQL Server | Microsoft Docs
So... have you ever done this successfully with an enterprise geodatabase in SQL Server? Any gotchas, hints, suggestions, soothing sounds, pointing and laughing?