We're still using SqlServer 2000 in most of our products and a switch to 2005 is currently not possible. I want to ask if there is way we can install TFS without everyone changing their configuration files to use a named instance of SQL Server 2000.
Default instance not SQL Server 2005
Hot Topic
- Problem with SharePoint when creating a project in TFS beta3
- Add a new work item type
- Deployment Items not working
- Issues with saved results from load test
- the request failed with http status 404
- Team Foundation Web Services
- MS Project/TFS work items won't move when linked
- sqlservr memory usage at 2GB
- S Rule to check String.Empty is used instead of ""
- static member variables and static constructor
VS Team System
- config files while testing
- Distributed System template generates VB code
- C/C++ Analysis - Incorrect C6293 warning
- Validating fields
- Adding a Team Server
- Version Control entry in Team Explorer won't show files/folders
- Process templates
- How to install sharepoint/team system in production server?
- Error while generating 'Issues' report
- field (System.Description) mapping with ms project in FileMapping.xml
Default instance not SQL Server 2005
AlExtjAi
The SQL Server repository part of TFS is only accessed by elements installed in the Team Foundation Server application tier installed on the server side. Client machines access TFS using an api over a collection of web services. None of your end users would normally point directly to the SQL 2005 database.
Cristianoq
Team Foundation does require that SQL 2005 be the default instance. We have some specific checking for this in V1.0. And, at the moment we don't have a direct way to support named instances via Setup. (note: we are looking into this for the future).
So, you might be able to find a way to get your other users to use named instances but TFS is going to demand the default instance.
marc