Are there any benefits of having a smaller database file?
Say you have a genuine reason for shrinking a database (re-claiming space after applying retention)... With exception to the obvious available disk space reclaim, are there any underlying benefits of having your database smaller in size on disk?
From a SQL perspective, recover-ability would be one. If the file is large (meaning you don't shrink) upon restore SQL will still carve out that space (even empty) so it could slow down your restore times. You have to weigh that against the likelihood that the file will grow again at some point after you shrink it. I tend to NOT shrink things unless absolutely necessary. This is also where things like instant file initialization (IFI) comes into play. Also a fast disk I/O subsystem would help to mitigate that issue. From an sysadmin perspective, I could maybe see something like SAN block replication where a large database would be an issue. There could be other 3rd party stuff in this realm that might not like a large database. NOTE: I'm not a sysadmin. There is a time and place to shrink just like with everything else. ;-) Hope that helps!