Geeks With Blogs
Gaurav Bodar - ALM Consultant, TFS specialist ALM, TFS, Agile, Scrum, Sharepoint, IT Service

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


SELECT DISTINCT DB_NAME(dovs.database_id) DBName,

dovs.logical_volume_name AS LogicalName,

dovs.volume_mount_point AS Drive,

CONVERT(INT,dovs.available_bytes/1048576.0) AS FreeSpaceInMB

FROM sys.master_files mf

CROSS APPLY sys.dm_os_volume_stats(mf.database_id, mf.FILE_ID) dovs




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. 

Posted on Monday, April 4, 2016 9:23 AM team foundation server , migration , TFS 2015 Upgrade | Back to top

Comments on this post: TFS 2015 Upgrade Issues with Diskspace

# re: TFS 2015 Upgrade Issues with Diskspace
Requesting Gravatar...
we looking for freelance to upgrade our TFS
please contact
Left by shlomo on May 16, 2016 11:18 PM

# re: TFS 2015 Upgrade Issues with Diskspace
Requesting Gravatar...
Also, create pre-provisioned environments for training and demonstrations.
Left by monstration on Jul 29, 2016 6:28 PM

comments powered by Disqus

Copyright © Gaurav Bodar | Powered by: