TFS 2015 with SQL Server 2014. Best migration path to upgrade to Azure DevOps 2019?
I am currently running TFS 2015 Update 3 with a SQL Server 2014 backend database environment.
It appears that SQL 2014 isn't supported with Azure DevOps 2019, so an in-place upgrade of TFS 2015 to 2019 may not be supported.
I have a separate SQL Server 2017 environment set up on a different server. My initial thought was to migrate TFS 2015 databases from SQL 2014 to SQL 2017 and then perform the upgrade. However, TFS 2015 doesn't support SQL 2017 (based on system requirements doc)
What would be the best migration path to upgrade from TFS 2015 to Azure DevOps 2019 while on SQL 2014 and only having SQL 2017 as an option?
TFS 2015 with SQL Server 2014. Best migration path to upgrade to Azure DevOps 2019?
You could upgrade your TFS application and your SQL serverl separately, not necessarily as a whole.
According to the document Upgrade your deployment to the latest version of Azure DevOps Server, we could upgrade the TFS 2015 to Azure DevOps Server 2019:
So, we could:
- Upgrade from SQL Server 2014 to SQL Server 2017
- Migration from TFS 2015 to Azure DevOps Server 2019
- Select the SQL Server 2017 when you configure databases
Note: Do not forget to backup all your data before upgrading.
You could check this document and this doc for some more details.
Hope this helps.
- View is not found when a Web App is deployed with Azure DevOps
- Re-checking for merge conflicts in VSTS (Azure DevOps)
- How to pass Environment Variables to Helmfile Values file
- Create a new pipeline from existing YML file in the repository (Azure Pipelines)
- How to reference a secret variable from an AzurePowerShell@5 task
- How can you insert suggestions on a PR in Azure Devops?
- .Net Core - Use AzureAD/EntraID Authentication to Access Azure DevOps REST APIs
- Azure-DevOps clone shows references as warnings
- Is it possible to rename a release?
- How to assign test point to a tester in Azure DevOps with API
- Access Azure Devops Query Results Using C#
- What does --runAsAutoLogon do when configuring an Azure Devops Windows self-hosted agent?
- How to Simplify a Complex Azure DevOps Release Pipeline with 11 Environments and Unique Task
- How to export multiple Azure DevOps Variable Groups?
- Passing branch names between pipelines
- Show list of work items I am following in VSTS?
- Prevent Azure Pipelines from failing build: No Agent Found in Pool which satisfies demand
- How do I get my Azure DevOps Pipeline build to fail when my linting script returns an error?
- Encountered conflicts when cherry-picking commit . This operation needs to be performed locally error in Azure DevOps
- Adding / setting Virtual Applications (Path mappings) to a Web App (App Service Azure) - via Powershell Script
- How do I filter releases for a specific Environment (Stage)?
- Python Script to crawl ADO Project for specific file and download it
- Run pre-built artefact in azure yaml pipeline
- Getting the Branch ID for Accesscontrol
- How do I trigger a failure in azure pipelines when a bicep template build fails?
- roleAssignment with current user id
- How can I inject Azure DevOps pipeline run number in a build artifact file?
- Cannot delete a branch which has policies
- Add reviewer automatically based on condition not coming from changes
- How can new NuGet packages in an upstream view be pushed to my feed automatically?