Is a TFS branch a physical or logical snapshot?

Question

When code is branched in TFS using the branch method, is the code physically or logically branched? By logical, I mean is it just a changeset (changed deltas) or are all of the files copied?

Answer 1

Branched files are not copied within the TFS database. A new version of the file will not be created until the branched version is modified. This is why creating a branch on a large project does not take forever.

Source:

http://www.codeplex.com/BranchingGuidance/Wiki/View.aspx?title=Isolation%20for%20Collaboration&referringTitle=Home

The fourth paragraph under branching explains that it does not create a separate copy of identical files:

Creating branches uses very little additional storage space. The server minimizes the storage required by only keeping one copy of identical content no matter how many different files are contained in the folder. So, if you have 100 copies of a 1 MB file and all of the files are identical, the server will store only 1 MB, not 100 MB. When you create a new branch and commit, all of the files in the new branch that are identical to the files in the source branch point to the same content. The result is that a branch consumes very little additional storage space, and that storage space expands only when the branched file becomes different than the source. And even when files change, Team Foundation Server employs a differencing engine to analyze changes between files and once again optimize storage space.

Microsoft Branching Guidance PDF:

http://geeks.netindonesia.net/downloads/etc/TFS-Branching.pdf

Answer 2

Short answer: Branches are stored logically and are not a direct copy of the parent.

Long answer: Bill Heys, a VS ALM Ranger, wrote a detailed blog post describing how branches and file history are stored in TFS.

http://blogs.msdn.com/b/billheys/archive/2011/05/05/how-tfs-stores-files-and-calculated-deltas-on-versioned-files.aspx