Tag Info

New answers tagged

-5

My work around for the Replication that is blocking shrinking log file is: Set DB Recovery Model to Simple Take DB offline Create backup of log file (just in case) Delete log file Bring DB online In my case it worked. After bringing DB online log was created automatically and it's size was 512kb instead of 70GB. But this is only a workaround. The root ...


5

What you are saying is right. The database should not be shrinked. However there are some exceptions. Let's say you move a lot of historical data out of your DB and it goes down from 100GB to 10GB. You may want to reduce it back to 10 or 20 or 50GB. The thing to remember when you decide to go on with a shrink is that data (clustered and non clustered ...



Top 50 recent answers are included