Tfs_sreetfs12_DefaultCollection –collection database Tfs_sreetfs12Configuration – the configuration database Right click on Databases and choose Restore and select the database to be restored by browsing to the physical location of the backup.Ĭonnect to the analysis services from SQL management studio and restore the Tfs_Analysis database as well. Restore the databases to the new SQL server to be used with TFS by connecting to the target SQL server from SQL management studio. The backup for the analysis database will be an. bak files.Ĭonnect to the Analysis services which hosts the Analysis database for TFS from SQL Management studio and backup the below database: Connect to the SQL server Database Engine that currently hosts the TFS databases from SQL Management studio and backup the below databases by right clicking on the database and then choosing Backup from the Tasks option: Run the below commands to stop the TFS services and ensure that users will not be able to connect to TFS during the outage window:īackup the TFS databases which you are planning to migrate to the new SQL server. Specifies the name of the Analysis Services database to be used with TFS if you have more than one such database on the server that you specified with the Specifies the name of the server and instance that now hosts SQL Server Analysis Services. If you are specifying more than one server, you must use a comma to separate multiple pairs of server and instance names. : Specifies the name of the server that is running SQL Server, in addition to the name of the instance if you want to use an instance other than the default instance. Specifies the name of the new SQL server that hosts the databases for TFS, in addition to the name of the configuration database. “Drive:\Program Files\Microsoft Team Foundation Server 12.0\Tools”īelow are the descriptions for the parameters used in the commands that should be run during the migration process. The TFS commands used in this article should be run from an elevated command prompt, in the below location: So plan accordingly and notify the users in advance. The migration activity will require an outage window, depending on the size and number of databases. The below article provides a step by step description on migrating the TFS databases for Team Foundation Server 2010 version, and has been used as a reference for writing this blog The migration process will involve the backup and restore of the databases to the new SQL server and then running commands to remap and register the new location of the databases with TFS application tier. SharePoint: should be a member of the farm administrators group TFS: Team Foundation Administrators and Admin Console UsersĪnalysis server: should be a member of the server administrators group. Servers: Administrators (local Administrators group or equivalent)
SQL, Analysis and Report Server: 2012 with SP1 Ø Central Administration Content DatabaseĪll the services (TFS, SharePoint and Reporting) will be running on the existing machines, only the backend databases will be moved to a different SQL server or an instance.īelow are the versions of products that have been used for the preparation of this blog The names of these databases may be different based on your configuration. The names of these databases may be different in your deployment of TFS. Ø Analysis Databases (Tfs_Analysis, if Reporting is configured with TFS) Ø Warehouse (Tfs_Warehouse, if Reporting is configured with TFS) Ø Collection Databases (Tfs_ there can be multiple databases, depending on the number of collections you have) Ø Configuration database (Tfs_Configuration) The databases to be migrated will depend on your deployment of TFS, and the components for which you choose to move the databases. This article will be helpful if you are planning to move the databases used by your TFS deployment, to a new hardware.
0 kommentar(er)
