During the last weeks we have been working on cleaning the TFS Version Control from old files. We encountered some unexpected problems, most of which was caused by the fact that the hard drive that holds the database only is 70 GB. The size of the database was around 30 GB and the files to be destroyed were around 15 GB. What we found was that destroying large amounts a data also requires large amount of disk space.
The destroy-command marks the files to be destroyed and a scheduled job is run each night to perform the actual destroy. This job can also be invoked manually from SQL Management Studio.
When the TfsVersionControl Administration Job is run the transaction log is filled with up to 2.5 times the size on the data that should be destroyed. That means that before the transaction is committed the size of the log in our case was around 40 GB. This meant that before the transaction could be committed we ran out of disk space and the job was cancelled.
With some modifications on my TFS Cleanup Tool we destroyed the files in smaller chunks which solved our problems at this time...
The destroy-command marks the files to be destroyed and a scheduled job is run each night to perform the actual destroy. This job can also be invoked manually from SQL Management Studio.
When the TfsVersionControl Administration Job is run the transaction log is filled with up to 2.5 times the size on the data that should be destroyed. That means that before the transaction is committed the size of the log in our case was around 40 GB. This meant that before the transaction could be committed we ran out of disk space and the job was cancelled.
With some modifications on my TFS Cleanup Tool we destroyed the files in smaller chunks which solved our problems at this time...
Comments
Post a Comment