Managing Team Foundation Server in a Workgroup

January 25, 2006 Jan 25, 2006 01/25/06
vstsuetb
Managing Team Foundation Server in a workgroup environment is possible but can present some challenges. Active Directory environments are recommended for most Team Foundation Server deployments. If Team Foundation Server is to be deployed in a workgroup, it should only be deployed in workgroups with a very limited number of users and computers...

Using Cumulative Flow Diagrams in User Education

January 11, 2006 Jan 11, 2006 01/11/06
vstsuetb
Hi everyone,I'm David Chesnut; a programming writer on Team System. You may have seen some of my previous posts on our use of Scrum in UE on Rob Caron's blog. We have been using Scrum for over a year to manage development of our help topics for Team Foundation. In addition to Scrum we have adopted use of the cumulative flow ...

More about SQL and Team Foundation Server

January 10, 2006 Jan 10, 2006 01/10/06
vstsuetb
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, ...

Backing Up and Restoring Team Foundation Server Data

January 10, 2006 Jan 10, 2006 01/10/06
vstsuetb
Performing backups is an important component of managing your Team Foundation deployment. Implementing a well-planned backup and restore strategy protects your data against data loss due to damage caused by a variety of failures. Testing your strategy by restoring a set of backups and recovering your database prepares you to respond ...

Planning for Disaster Recovery

January 10, 2006 Jan 10, 2006 01/10/06
vstsuetb
Planning ahead is important for effective disaster recovery of a Team Foundation deployment. You should understand the size and scope of your Team Foundation deployment, know the maintenance and backup schedule for Team Foundation Server, and create a disaster recovery plan. You should also consider simulating a disaster recovery situation and...

Planning for Backup and Restore

January 10, 2006 Jan 10, 2006 01/10/06
vstsuetb
Creating a backup and restore plan is a critical part of any Team Foundation deployment. In order to create this plan, you need to understand the size and scope of your Team Foundation deployment, designate a person or a team of people to perform backups, determine a backup storage strategy, and consider what backup software might best meet ...

Planning for Current Needs

January 10, 2006 Jan 10, 2006 01/10/06
vstsuetb
There are many aspects to consider when estimating your needs for a Team Foundation deployment. Understanding the size and scope of your current organization and understanding the requirements and limitations of Team Foundation Server deployment types will help you make the necessary planning decisions.Considerations When Estimating Current ...

Moving a Team Project from One Version to the Next

January 10, 2006 Jan 10, 2006 01/10/06
vstsuetb
If the team project you are managing has completed a major iteration or milestone, and has grown too large or is not compatible with the desired workflow going forward, you can create a new team project based on the existing one. Moving a team project from one version to the next involves some combination of branching source code, copying ...

Team Foundation Server Data Warehouse

January 10, 2006 Jan 10, 2006 01/10/06
vstsuetb
The data warehouse is a relational database organized in a star schema with an OLAP database derived from that database. The OLAP database allows the reporting tools to access the derived information without degrading the performance of the relational database that actually stores the real-time information from the clients.The warehouse stores...

Team Foundation Server Permissions

January 4, 2006 Jan 4, 2006 01/4/06
vstsuetb
Mike writes: "We need to configure the server to grant all users the ability to create a Team Project and manage the users of that specific project. However, a user must not be allowed to delete/modify/access a project which he or she does not belong to. Also, since users will belong to the Sharepoint administration group and SQL Server ...