Frank had a few questions about using SQL:P>
Another useful set of guidelines would be SQL for dummies or at least for TFSers…I don’t expect you to turn me into an SQL MVP, just give me the basics so I don’t need to figure them out for myself. How to back up and restore, how to control which drive (or drives?) the data are stored on, other best practices for avoiding future pain…”
Although I’d love to empart some meaningful words of wisdom, I probably won’t have enough to satisfy you. Team Foundation Server is built on SQL Server 2005 and uses SQL Server to store everything about work items, quality attributes, testing, test results, and build results. Team Foundation Server then uses SQL Server Analysis Services to aggregate and analyze the data and drive the reports. The reports that are created by the process template or by individual team members using Microsoft Excel or SQL Server 2005 Report Designer are made available through SQL Server 2005 Reporting Services and the team report site.
The reports already produced by Team Foundation can help you quickly assess the status of the team project, the quality of the software under development, and the progress toward project completion. These reports summarize the metrics from such things as work items, source control, test results, and builds. For example, the reports can tell you how fast your team is working from week-to-week, based on their actual activities. The process template used in creating the team project determines which reports are available by default, but you can also add your own custom reports. The content and use of each report created by the process template is explained in the process guidance for that template.
I can, however, provide links to documentation that has been released (or is in the pipeline for release very soon) that may help you decypher those pain points. I’m including information on the Team Foundation Server data warehouse, how you can plan for your current needs, planning for backing up and restoring your Team Foundation Server data, performing a restore of your Team Foundation Server data, moving your team project data (which may help you to figure out what to do when you’ve outgrown your first test project), and planning for disaster recovery – the ultimate pain point.
Thanks for the question, Frank.