Originally posted on: http://geekswithblogs.net/gauravtfs/archive/2016/04/04/tfs-2015-upgrade-issues-with-diskspace.aspx
Problem: TFS Collection Move, Upgrade would need
heaps of memory on tempdb
Resolution: If you are upgrading or moving your Large
Tfs Collection you might get the Error
Exception Message: TF30042: The database is full. Contact
your Team Foundation Server administrator. (type DatabaseFullException)
Exception Stack Trace:
at
Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.TranslateException(Int32
errorNumber, SqlException sqlException, SqlError sqlError)
You could run the query on SQL Server to review your
Database growth during Migration
SELECTDISTINCTDB_NAME(dovs.database_id)DBName,
dovs.logical_volume_nameASLogicalName,
dovs.volume_mount_pointASDrive,
CONVERT(INT,dovs.available_bytes/1048576.0)ASFreeSpaceInMB
FROMsys.master_filesmf
CROSSAPPLYsys.dm_os_volume_stats(mf.database_id,mf.FILE_ID)dovs
ORDERBYFreeSpaceInMBASC
GO
I figure out that I had Collection size of around 70 GB and
I needed 30GB for tempdb to do
successful migration. So you need to allocate about 40% disk space to your tempdb to your Collection size
to migrate it.
TFS 2008 used to come with separate Version Control,
Integration and Configuration Databases. It seems now also the whole Version
Control ( which is biggest space consumer) transfers with Single transaction.
