If you are running TFS and Visual Studio 2005 on the same machine (or VPC) you, after a little while of it being up you should notice that evrything is running slow (if you don't, you are probably spending too much money in hardware) and if you check, you will see high CPU utilization, primarily from msmdsrv.exe (SQL Server Analysis Services). The reason for this is that (apparently for demo purposes) the updates interval for the reporting warehouse database was set too low and the process takes a long time, therefore causing it to run almost constantly.
You can change the interval but keep in mind that doing so will delay the availability of the TFS data for reporting purposes, Buck Hodges posted the solution here
, but I'm copying it here just so that it appears in one more place, since people appear to keep facing this problem (hopefully it will be easier to find since it is in one more place out there on the 'net). After the instructions on how to change the interval setting, you will find instructions on how to force the Data Warehouse refresh in case you need the data and the automatic refresh has not taken place.
If you are not executing the following steps from the TFS Server machine in question, use the machine name instead of 'localhost'
Change the run interval on the app tier as follows.
- Stop TFSServerScheduler using 'net stop TFSServerScheduler'.
- Go to http://localhost:8080/Warehouse/warehousecontroller.asmx using a browser on the app tier. Click on ChangeSetting and enter the following values and then press the 'Invoke' button (3600 seconds = run once per hour).
- settingID: RunIntervalSeconds
- newValue: 3600
- Restart TFSServerScheduler using 'net start TFSServerScheduler'.
Note: It is important to restart TFSServerScheduler, as the interval is cached and will not take effect until the next run.
To manually kick off the data warehouse refresh follow these steps:
- Go to http://localhost:8080/Warehouse/warehousecontroller.asmx using a browser on the app tier.
- Click the ‘Run’ link.
- Press the ‘Invoke’ button.
Having no internet connectivity (more common if you are running on a VPC) will cause the Visual Studio help to run slow if you have it configured to check the online documentation. Make sure you set it to local-only. To do so, in the Visual Studio main menu select Tools > Options then in the treeview navigate to Environment > Help > Online
If you are not able to make it to TechEd this year... or even if you are... don't forget that there's more training that you can take advantage of. Visual Studio 2005 DevCon is just around the corner at these cities:
St. Louis, MO (5/26)
Chicago, IL (6/1)
Minneapolis, MN (6/1)
Kansas City, KS (6/2)
Omaha, NE (6/14)
Detroit, MI (6/14)
Dallas, TX (6/16)
There will be three tracks in the Agenda:
- ASP.Net 2.0
- Visual Studio Team System
- Smart Clients with Visual Studio 2005
You will walk out of there with a good brain cell work-out, three books and a Visual Studio Team System Beta DVD kit (among other things). Visit the official announcement for details and to register. If you are going to the one in Dallas... See you there!