Skip to main content

TFS Reports Out of Date

You may have noticed it takes a while for Team Foundation Server (TFS) reports to reflect changes you've made to work items or builds. Let me guess...about an hour, right? Out of the box, TFS is set to refresh the data warehouse from its transactional store every 60 minutes.

How do I change the frequency of the data warehouse refresh?
  1. Browse to the TFS Controller Web Service on your TFS application tier server within IE at: http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx
  2. Select the ChangeSetting option
  3. Enter RunIntervalSeconds for the settingId and the desired number of seconds for newValue (300 for 5 minutes...5*60)
  4. Select Invoke

refresh-0

How do I force a data warehouse refresh?

Two methods here: either via the above web service or using SQL Server Management Studio.

Via the web service:

  1. Browse to the TFS Controller Web Service within IE at: http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx
  2. Select the Run option
  3. Click Invoke
  4. You should expect a new browser window opening along with an XML fragment with the element reporting true. If false, something went awry.
  5. Close the browser
  6. Click "Click here for a complete list of operations"
  7. Click GetWarehouseStatus
  8. Click Invoke
  9. You should see either idle (it completed) or running

Via SQL Server Management Studio:

  1. Open SQL Server Management Studio
  2. Authenticate with Analysis Services
  3. Drill into Databases to TfsWarehouse
  4. Right-mouse selecting Process
  5. Click Ok, and finally Close when processing completes

refresh-1

My reports still aren't refreshed and reflect an old refresh date. What gives?

For performance and scalability, SQL Server Reporting Services (SSRS) caches reports. By default, it's set to expire the cache every 30 minutes. On a per-report basis, you may change or even eliminate this caching behavior:

  1. Browse to SSRS using IE at: http://localhost/Reports/
  2. Select a report
  3. Click the Properties tab...Execution option
  4. In a production setting, you might dial back the sliding scale from 30 to 15 or 20 minutes. Because I frequently perform demos, I actually eliminate the caching.

refresh-2

Labels

Labels:

Comments

Anonymous said…
Thanks man, you saved me some serious frustration!
Friday, January 30, 2009 3:52:00 PM
Robaticus said…
Old post, but a good post. Is there any guidance for the frequency of updates? I know the default is 1 or 2 hours, but is there any harm if we set the update to every 5 minutes?
Tuesday, September 22, 2009 1:50:00 PM
Jeff Hunsaker said…
@Robaticus Not that I've ever seen. I think you'd want to monitor your data tier performance and look at responsiveness. And, obviously, you'd want to make sure the refresh occurred within a 5 minute window. :) Finally, if you're not caching within SSRS, this would render reports without data. Potentially a poor user experience.
Tuesday, September 22, 2009 9:43:00 PM
Jeff Clark said…
Thanks Jeff
Thursday, June 17, 2010 2:45:00 PM
Anonymous said…
Good stuff, one other thing to consider is, if you view your reports through a SharePoint dashboard the SharePoint server may also be caching the report. Hmmm
Thursday, July 01, 2010 6:47:00 PM
Anonymous said…
Link for TFS 2010 is;
http://localhost:8080/tfs/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx
Thursday, January 19, 2012 1:39:00 AM
Post a Comment

Popular posts from this blog

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki...
10 comments
Read more

Certified or Certifiable?

As a senior technology professional, I interview a lot of candidates. I also maintain solid relationships with other folks in the community. Frequently, the topic of certifications arises: A good investment? Valuable? A clear measurement of skill? Consensus appears to draw the line related to one's seniority. If you're (for example) just out of school and looking for an instant creditability boost, by all means pursue a certification. Likely, this credential will assist you in overcoming the "junior" tag and likely land you more interviews and client roles. (Note: I'm going to use the terms senior and junior here...no offense to either. Can't think of a better one word description. I was a junior once too.) In stark contrast, the value of certifications drops off the table around the 2-3 year mark. Some in my circles even perceive certifications as a negative for the senior professional. They think, "If this guy is so solid, why is he wasting valuable...
5 comments
Read more