12 дек. 2019 г. · As far as the SQL Server product is concerned, the SHRINKFILE operation is safe. It is designed to respect locks, recovery models, ...

14 дек. 2020 г. · They both do the same thing in the end. But SHRINKFILE is better since it gives you better control. You decide which file to shrink and to what size you want ...

24 авг. 2019 г. · Yes, it is safe to cancel that operation (but you need to be patient and let it finish rolling back - do not panic and stop the SQL Server service or reboot ...

1 мая 2012 г. · A reorganise-and-shrink is never recommended really. If you can take the apps the database is serving offline, you can speed up the process ...

14 дек. 2020 г. · DBCC SHRINKDATABASE does not rollback when the process is killed so theoretically you'd be able to run it for a period of a time, kill the process, and have ...

23 нояб. 2013 г. · Yes, do the actual shrink - Consider using DBCC SHRINKFILE instead of DBCC SHRINKDATABASE , you have more control over what gets shrunk and how.

21 окт. 2014 г. · This stored procedure has a column “ Percent_Complete ” which gives you how much % shrinking of database is been completed by Server.

2 авг. 2017 г. · DBCC SHRINKFILE might not block production activity. Then again, it might. It's safest to plan this during a planned outage.

23 апр. 2010 г. · Is it safe to run DBCC ShrinkFile at any time? Will running DBCC ShrinkFile cause performance issues to users querying DB at same time?

15 янв. 2021 г. · No, shrink is safe. Unless you hit some bug in SQL Server of course, but that can happen whatever you do.