I am trying to find path to migrate TFS 2018 (OS Win 2016, SQL Server 2017) to a new machine with OS Win 2019 and SQL Server 2019.
On new machine I am planning to install Azure Devops 2020, but I am not sure about migrations steps.
Will I first do migration of TFS databases from TFS 2018 (migration db and objects)?
After that I will install Azure Devops 2020 with point to migrated/restored DB from TFS2018.
I am confused, about documentation, because I found that I need to do whole process of upgrade on old TFS2018 machine (OS->2019, DB->2019, TFS ->Azure Devops), and after that migrate to new machine.
But I hope that I can do migrate/restore DB on new SQL Server 2019, and after that during Azure Devops 2020, choose restored DB and etc...
Please any info would be appreciated
Thank you for your time,
Keli
Using the TFS Admin Console backup your existing TFS databases.
Copy the backup files to the new SQL server and restore them
Install Azure DevOps Server on the new target server but don't configure it
On the new Azure DevOps Server use Scheduled Backups - Restore Databases
I believe this will work if the source server was 2017 or later.
Thanks Rob, for response.
I succeeded, but my path was a little different because I had TFS server with SQL Enterprise Edition, and I needed to do migration of databases to 2019 Standard Edition:
Install new virtual machine (VMNew) with: Windows 2019, SQL Server 2019 (Standard Edition).
On this machine I install Azure Devops 2020, but I didn't configure it.
On my TFS server (Windows 2016, SQL 2017 Enterprise Edition) I did
backup all databases with TFS administration console
On new VMNew server, with Azure Devops Console, I did restore databases, but only
ConfigurationDB and CollectionDB.
Restore of ReportingServicesDB and WarehouseDB wasn't possible, because
my old TFS server was SQL Enterprise Edition.
After successfully restored ConfigurationDB and CollectionDB on VMNew, I
configured Azure Devops feature through Console. And site is started successfully.
ReportingServices and Warehouse I configured after step 4. also, through
Azure Devops Console.
Hope that this info will help someone.
Kind regards,
Keli
Related
I'm a little confused over the latest released versions of Azure DevOps Server 2020 on 17th May.
What is the difference between 2020.0.2 and 2020.1.2 and why are two versions of 2020 being maintained?
Currently running 2020.0.1 and looking to move to latest version.
The main difference should between Server Version RC and RTW. The data migration tool doesn't support imports from Azure DevOps Server release candidates (RC). If you're planning on importing your collection database to Azure DevOps Services using this service, it's important that you don't upgrade your production database to an RC release. If you do upgrade, then you will need to wait and upgrade to the release to web (RTW) version when it's available or restore a backup copy of your database from a previous Azure DevOps Server version to import.
From the Release on May 17, 2022, along with several fixes, the Data Migration tool will be available for both Sever 2020.0.2 and 2020.1.2
Before preparing for upgrade, check this official doc: Upgrade your deployment - Azure DevOps Server & TFS | Microsoft Docs
We have recently upgraded to Azure DevOps 2020 on our testing environment, previously we had TFS 2017 and then upgraded Azure DevOps 2019 and now to Azure DevOps 2020.
I am facing issue regarding the agents I had configured in the earlier version. They don't see to update when I click on the update agent link.
I have one agent i.e. POC_2017Agent installed and created with TFS 2017 agent and the last two agents were created and installed with Azure DevOps 2019.
After we upgraded to 2020 all 3 of them are shown as Offline, even when their services on the servers are running\restarted.
How can I upgrade the agents manually, if they are not getting upgraded automatically after clicking on the update Agent link?
I don't want to remove them and reconfigure again.
Beginning with Azure DevOps Server 2019, you can configure your server to look for the agent package files on a local disk. This configuration will override the default version that came with the server at the time of its release.
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops-2019&tabs=browser#can-i-update-my-v2-agents-that-are-part-of-an-azure-devops-server-pool
I bought a license to use Azure DevOps 2020 and a license came to use SQL Server 2019 Standard.
Where do I see how many processor core I can use on the server for this SQL Server license?
" Microsoft SQL Server 2019 Standard is included with the Azure DevOps Server license for use
with Azure DevOps Server"
Thank you.
According to your description, seems this issue is not related to Azure DevOps side.
You could refer below tables which shows a comparison of the key capacity limits across the SQL Server 2019 editions.
For more detail info please refer our official doc here:
Microsoft SQL Server 2019 Licensing guide
sql-server-2019-pricing
Besides, suggest you directly connect with a Microsoft solution provider in order to get a more concreted idea of this area.
I just started working for a company that is still using SQL Server 2008 R2. We have many stored procedures, SSIS packages, and SSRS reports.
Plan to start doing additional .Net development as well. We currently do not have any source control and code is stored in a combination of someones local disk as well as network share.
My manager is open to suggestions and I would like to propose Azure DevOps as I do have experience working with it from other companies. Also our department is expected to grow over the next few years and I think it would be good to use Azure DevOps as a good foundation.
Lastly, I want to suggest to my manager that we use the Azure Scrum board for tracking development and I think that it will be great to "tie" work from the scrum board to ADO releases.
My questions:
Will SQL Server / BIDS 2008 (SSIS, SSRS) work with Azure DevOps? I assume so, but I'm not sure if there are any "gotchas" that may prevent it from working correctly.
Will SQL Server/BIDS 2008 work with the Azure CI/CD pipeline?
Thanks!
From this doc:
Azure DevOps Server is the on-premises offering that's built on a SQL
Server back end. Customers usually choose on-premises when they need
their data to stay within their network or when they want access to
SQL Server reporting services that integrate with Azure DevOps data
and tools.
Since you need to Azure Devops work with Sql Server, you could use the Azure Devops Server.
For example:SSRS reports are available from Azure DevOps Server or TFS when configured with SQL Server Analysis Services.
But azure devops server has requirements for the version of sql server.
The Sql server 2008 only supports TFS 2010 and TFS 2012. If you want to use a newer version of Azure Devops server/TFS, you need to upgrade your Sql Server.
Here is the detailed Sql Server requirements about the Azure Devop.
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.