AnsweredAssumed Answered

Any problems with shrinking enterprise geodatabase in SQL Server?

Question asked by tminterWork on Feb 6, 2020
Latest reply on Sep 4, 2020 by tminterWork

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:


While the Microsoft help is not:


So...  have you ever done this successfully with an enterprise geodatabase in SQL Server?  Any gotchas, hints, suggestions, soothing sounds, pointing and laughing?