Deploying TFS in the Developer Division at Microsoft

re: Deploying TFS in the Developer Division at Microsoft

Maximilian Haru Raditya — Wed, 17 May 2006 18:47:32 GMT

Cool!

I really like what's been explained in your post. It shows me a real case study, especially when you said that MS is currently using it internally for the developer division. Is it almost all parts of the division?

I absolutely agree with you that the next version of TFS should provide an option to move data warehouse server (the analysis service server, furthermore the reporting service sever as well) to servers other than the transactional database server for maximum scalability.

Also, I think TFS should support installation on 64-bit machine to scale well for the next version, not just the SQL Server part, which is currently the only supported scenario.

I think it's really a good work for a V1 product.

Thanks and keep up the good work!

re: Deploying TFS in the Developer Division at Microsoft

KeithH — Wed, 17 May 2006 19:50:30 GMT

It's great to see you guys following through on pushing TFS into DevDiv. It's this kind of "extreme" dogfooding that reassures me that our paltry sized (in comparison) development teams won't hit these issues because you will have found & fixed them first. I'm looking forward to SP1. BTW is there any chance that we will get a "move team project" utility to move a project from one TF server to another in SP1?

re: Deploying TFS in the Developer Division at Microsoft

Bryan Hinton — Wed, 17 May 2006 20:09:44 GMT

Brian,

Thanks for sharing - I have been part of a TFS pilot program here at Intel and am trying to evangelize its use and having this information is very valuable to back up my efforts. Could you also share the queries that you are running to get the statistics you listed? I would like to do similar things for my system.

re: Deploying TFS in the Developer Division at Microsoft

bharry — Thu, 18 May 2006 14:48:37 GMT

Thanks for the comments so far. I'm going to roll up some responses to the first 3 comments in one.

No, we're not nearly to all parts of the division yet. I'd guess we're in the ballpark of a 3rd of the way - maybe a little less on file count.

No, I'm afraid "move team project" is much more work than we can do in a service pack. However, we are already working hard on it for our next release.

I'll post some of the queries I use in my next blog post. Yesterday I spent a couple of hour tuning them because it was starting to take quite a few minutes to gather all of the statistics. I'll try to get that out by the end of next week.

Thanks again and keep the comments and questions coming...

Brian

VSTS Links - 05/18/2006

Team System News — Thu, 18 May 2006 22:48:43 GMT

Brian Harry gives an excellent post on Deploying TFS in the Developer Division at Microsoft.

James...

DevDiv내의 TFS 사용에 관한 글

bkchung's WebLog — Sun, 21 May 2006 18:45:20 GMT

http://blogs.msdn.com/bharry/archive/2006/05/17/599817.aspx
DevDiv는 Developer Division의 약자로 제가 속한 디비젼으로...

shoemoney

shoemoney — Fri, 02 Jun 2006 00:17:03 GMT

nice shoemoney site at <a href="http://www.imyourhuckleberry.info/">shoemoney</a>">http://www.imyourhuckleberry.info/">shoemoney</a> http://www.imyourhuckleberry.info/ 16

re: Deploying TFS in the Developer Division at Microsoft

Carl Daniel — Mon, 12 Jun 2006 19:31:09 GMT

Great article, Brian! How's that next blog post coming - you know, the one with the queries you use to get TFS statistics?

re: Deploying TFS in the Developer Division at Microsoft

bharry — Mon, 12 Jun 2006 23:21:02 GMT

Sorry about that, I just posted them

re: Deploying TFS in the Developer Division at Microsoft

Minas Casiou — Thu, 15 Jun 2006 06:35:54 GMT

TFS Server Error on Branching (about 5GB of data in main branch)...
SQL Error..>See below...

------------
String or binary data would be truncated.
MRPTEST2.TfsVersionControl..prc_PendBranch: Database Update Failure - Error 8152 executing INSERT statement for tbl_Lock
The statement has been terminated. (type SqlException)
------------

An error report has been generated & sent off etc.
Is there anywhere I can get patches for this bug by any chance?
The Branch operation worked on the main branch in the past, and still works for small parts, but the whole of the trunk can no longer be branched! :( Spewing! Just at the last part of our eveluation process!!!

TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 15/06/2006 3:07:13 AM
Machine: MRPTEST2
Application Domain: /LM/W3SVC/3/Root/VersionControl-3-127948074529668170
Assembly: Microsoft.TeamFoundation.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 2672
Thread Id: 3992
Account name: NSWPS\n1115635

Detailed Message: TF14105: An exception occurred in the Team Foundation Source Control System.
Web Request Details
Url: http://mrptest2:8080/VersionControl/v1.0/repository.asmx [method: POST]
User Agent: Team Foundation (devenv.exe, 8.0.50727.147)
Headers: Content-Length=585&Content-Type=application%2fsoap%2bxml%3b+charset%3dutf-8&Accept-Encoding=gzip&Accept-Language=en-AU&Expect=100-continue&Host=mrptest2%3a8080&User-Agent=Team+Foundation+(devenv.exe%2c+8.0.50727.147)&X-TFS-Version=1.0.0.0&X-VersionControl-Instance=f755ccec-a571-4ddd-92bc-b5cbdb71e9b8
Path: /VersionControl/v1.0/repository.asmx
Local Request: True
Host Address: 10.12.112.60
User: NSWPS\n1115635 [authentication type: NTLM]

Exception Message: String or binary data would be truncated.
MRPTEST2.TfsVersionControl..prc_PendBranch: Database Update Failure - Error 8152 executing INSERT statement for tbl_Lock
The statement has been terminated. (type SqlException)
SQL Exception Class: 16
SQL Exception Number: 8152
SQL Exception Procedure: prc_PendBranch
SQL Exception Line Number: 570
SQL Exception Server: MRPTEST2
SQL Exception State: 13
SQL Error(s):
SQL Error[1]: System.Data.SqlClient.SqlError: MRPTEST2.TfsVersionControl..prc_PendBranch: Database Update Failure - Error 8152 executing INSERT statement for tbl_Lock
Class: 16
Number: 500004
Server: MRPTEST2
Source: .Net SqlClient Data Provider
State: 1
Procedure: prc_PendBranch
Line Number: 597
SQL Error[2]: System.Data.SqlClient.SqlError: The statement has been terminated.
Class: 0
Number: 3621
Server: MRPTEST2
Source: .Net SqlClient Data Provider
State: 0
Procedure: prc_PendBranch
Line Number: 570

Exception Data Dictionary:
HelpLink.ProdName = Microsoft SQL Server
HelpLink.ProdVer = 09.00.2047
HelpLink.EvtSrc = MSSQLServer
HelpLink.EvtID = 8152
HelpLink.BaseHelpUrl = http://go.microsoft.com/fwlink
HelpLink.LinkId = 20476

Exception Stack Trace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.TeamFoundation.Server.SqlResourceComponent.execute(ExecuteType executeType, CommandBehavior behavior)
at Microsoft.TeamFoundation.VersionControl.Server.VersionControlSqlResourceComponent.execute(ExecuteType executeType, CommandBehavior behavior)
at Microsoft.TeamFoundation.Server.SqlResourceComponent.ExecuteReader()
at Microsoft.TeamFoundation.VersionControl.Server.VersionedItemComponent.PendBranch(Workspace workspace, String sourceServerItem, String targetServerItem, List`1 dontBranch, IList gets, IList failures)
at Microsoft.TeamFoundation.VersionControl.Server.ChangeRequest.PendChange(ExpandedChange expandedChange, VersionedItemComponent db, Workspace workspace, IPrincipal userPrincipal, Set`1 attempts, IList successes, IList warnings, IList failures)
at Microsoft.TeamFoundation.VersionControl.Server.ChangeRequest.PendChanges(IPrincipal userPrincipal, Workspace workspace, ChangeRequest[] requests, ArrayList& failures)
at Microsoft.TeamFoundation.VersionControl.Server.Repository.PendChanges(String workspaceName, String ownerName, ChangeRequest[] changes, ArrayList& failures)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

re: Deploying TFS in the Developer Division at Microsoft

bharry — Thu, 15 Jun 2006 15:35:36 GMT

I just sent it to the dev team and I'll let you know what I hear.

re: Deploying TFS in the Developer Division at Microsoft

bharry — Fri, 16 Jun 2006 21:39:39 GMT

Here's what I got back:

It looks like the most likely cause of this is one of the items in the target of the branch exceeds 260 characters. There is an error check which checks for it – but due to a faulty join, it requires the target of the branch to be mapped in the working folders. Our assumption is that the target is not mapped – skipping the error check and failing when it actually inserts into tbl_Lock. If the customer maps the target of the branch – it will give them the item which is too long. This has been fixed in SP1.

So it sounds like fundementally the problem is that you are trying to branch a tree that is resulting in a path that is greater than 260 characters. You need to branch it higher in the tree and/or use a shorter foldername. TFS can only store paths up to 260 characters long.

Let me know if this doesn't seem like the problem.

Brian

re: Deploying TFS in the Developer Division at Microsoft

Messaoud — Fri, 23 Jun 2006 18:34:56 GMT

Interresting.
Can you tell us more about the size/physical configuration of the server you used ?
Some info about :
- nb of Servers
- CPUs
- RAMs
- HD

Thanx,
Messaoud

Visual Studio Team System Resources (VSTS)

Sean McBreen's WebLog — Wed, 06 Dec 2006 06:26:26 GMT

I'm very proud of Visual Studio Team System and what Microsoft have done here - I've blogged about it

Bored? Want to find out what it was like for MS to deploy TFS?

Darryl Burling @ Work — Tue, 19 Dec 2006 06:40:31 GMT

In case you have become bored due to us not releasing anything since Saturday ( Visual Studio 2005 SP1

ALM using VSTS / TFS - More links than you shake a stick at !

The Liquidator — Thu, 01 Feb 2007 09:00:54 GMT

Configuration and Management of Team Foundation Server http://msdn.microsoft.com/vstudio/teamsystem/team/quickstarts/configure/default.aspx

Brian Harry: Microsoft DevDiv Dogfood Statistics — Version Control Blog — Microsoft Team Foundation, Use cases,

Sat, 10 Feb 2007 00:48:32 GMT

PingBack from http://versioncontrolblog.com/2007/02/10/brian-harry-microsoft-devdiv-dogfood-statistics/

re: Deploying TFS in the Developer Division at Microsoft

Stern — Sat, 10 Feb 2007 12:38:01 GMT

Replying to an old post, but "TFS can only store paths up to 260 characters long" - that's kind of rubbish, isn't it?

re: Deploying TFS in the Developer Division at Microsoft

bharry — Sat, 10 Feb 2007 14:52:46 GMT

I don't particularly think so. There's no doubt it's a limitation and it will affect some people but not very many. The reason for this limit is that the Win32 API only supports 259 character paths using the normal syntax. To support paths with longer than 259 character, they have to be prefixed with \\?\. It's not that it's amazingly hard to do but there is some work in it and it is relatively poorly understood. The result is that very few apps support more than 260 character paths.

Let's think a bit about what a 260 character path means. With an 80 character wide console window, it wraps around the screen more than 3 times. Not particularly legible.

That said, it's on our radar to get to removing the limitation because there are sometimes legitimate reasons for such long paths.

Brian