Is it a good idea to include "Shrink db Task" in the backup plan?
Posted on 2013-01-17
In our company backup plan, we have the following tasks prior to the Full db backup task:
Check Db Integrity (for all db, include indexes)
Shrink Db (for all db, Limit: 50mb, Free space: 10%)
Update Statistics (for all db, Object: Tables and views, All existing statistics, Full scan)
The problem is, these three tasks hours to complete -- sometimes the Shrink Db even takes 24 hours, which causes the Full db backup to be pushed back so much. This makes just no sense. So can you tell me what I should do?