Migration from TFS 2015 to Azure Devops Services - migration

Can i migrate from TFS 2015 to Azure Devops Services without upgrading TFS to other/latest version, if possible please do provide related documents.

This handy image from Microsoft will help
Yes, you can go from 2015.x to 2020.x
They also provide this note/warning
Before you upgrade to Azure DevOps Server 2020
When upgrading your on-premises deployment to Azure DevOps Server 2020 you should be aware that upgrade from TFS 2015 and later versions are only supported. If you are using TFS 2013 or earlier versions, you need to upgrade to TFS 2015 first.

Related

Download TFS 2015 Build Agent without TFS 2015 install

We currently use TFS 2013 with a suite of XAML builds, there are a few hundred projects here, each with an average of six build definitions each.
We're wanting to upgrade to TFS 2017 (2018 doesn't support XAML) but need to be able to support the XAML builds until they're all migrated.
According to MS, we can setup a TFS 2017 box, a build server with a 2017 build agent on it and a separate build server with a 2015 build agent on it which TFS can use to run the XAML builds.
My problem is... where to get the 2015 build agent installer from. Normally you ask TFS for the build agent installer, but we don't have a TFS 2015 installation.
Am I going to have to setup a TFS 2015 VM just so I can click one lousy link and download one installer. I've searched around but can't find any other place to get the damned thing from.
Anyone got a link to an MS page?
You could download the latest build agent from the link below:
Download Latest Agent , which will download the "vsts-agent-win7-x64-2.xxx.x.zip" file for you. Currently I believe that both TFS 2015 and TFS 2017 are downloading the same latest agent as mentioned above.
If you need a specific version of the agent you could take a look at the git hub for the specific Releases of the VSTS agents

which SSDT for VS 2017 when I have SQL Server 2016 DE

I have VS 2017 CE, SQL Server 2016 DE and Microsoft SQL Server Management Studio 13.0.16106.4. About VS is showing Microsoft SQL Server Data Tools as installed.
I would like to install SSDT so that I can do the SSRS/SSIS and SSAS but I don't know which one to install, it's giving few options from here
It reads
Download SQL Server Data Tools 17.1 for Visual Studio 2015
Download Data-Tier Application Framework (DacFx) 17.1
From the same website
It then advises "To use SQL Server Data Tools in Visual Studio 2017 see this section below". When I go to the link provided it takes me to visualstudio.com website. It's not apparent to me what I need to download from there, is it the Community Edition?
Going back to the first link I provided, it advises...
If you are using SSDT with Visual Studio 2017, install the AS and RS components:
Analysis Services
Reporting Services
I also found another link...www.visualstudio.com/vs/ssdt/
Also are there any conflict between sql server 2016 and vs 2017 CE when taking SSRS/SSIS or SSAS tasks?
StackOverFlow is giving me message that I need to have number of reputation before I can give more than 1 website link.
Can someone advise me which one to install?
Thanks.
For Visual Studio 2017, there is not yet a stand alone install of SSIS|AS|RS. However, there are VSIX installs available for RS and AS. See links below.
SSIS is working on creating a standalone install as well as a VSIX package.
https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio
https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftAnalysisServicesModelingProjects

Can I remove diagnostics.wadcfg safely now we have diagnostics.wadcfgx?

I have an WCF service on Azure with diagnostics/logging enabled. The project is already existing for some time and transitted through Visual Studio 2012, 2013 and now 2015. I discovered there is two diagnostics.wadcfg(X) files.
Can I remove diagnostics.wadcfg?
Where I can find some information on .wadcfg and .wadcfgx? Meaning what Microsoft Tooling was upgraded at some point in time that we now need .wadcfgx?
Thanks. BR, Rene
wadcfg can be safely removed and so is the reference to Azure Diagnostics -- assuming you've upgraded to Azure SDK 2.5+

Copy TFS 2012 collection to another server with TFS 2015 Installed

We have an old server machine with TFS 2012 installed on it. It has the 'DefaultCollection' of project collection. We want to copy (not move, i.e. leaving the collection in place) the 'DefaultCollection' collection to another machine which has TFS 2015 installed.
How can we do that please?
Thanks, ashilon
It depends a bit on how complicated your TFS installation is, but here are the steps for a simpler one server setup without Sharepoint:
Detatch the collection from your current TFS 2012 using the Team
Foundation Server Administration Console. This will copy the configuration into the collection database.
Take a full backup of the collection database (called something like Tfs_DefaultCollection) using SQL Server Management Studio (SSMS).
Restore the original collection on your TFS 2012 server
Re-attach the database on your TFS 2015 server using SSMS. Note that if you already created a collection on this server with the name DefaultCollection, you either need to delete/rename this or restore the cloned collection using a new name.
Attach the collection on your TFS 2015 server using the Team
Foundation Server Administration Console
Start the collection so that it get's into the Online state.
Please note that build servers, drop locations and so on will now point to same thing in the original collection and the clone collection, so you need to do a bit of cleanup.
The above is a shorter version of this: https://msdn.microsoft.com/en-us/library/dd936158(v=vs.110).aspx
Edit: I have successfully used the above approach to make a test migration from TFS 2010 to TFS 2013 RTM followed by the migration of our production environment. We use the server with the test migration for testing new updates before applying to production and we have done so with all updates from 2013 RTM until 2015 Update 3. I am currently applying the same approach in upgrading to 2017 in order to get a fresh server with never version of SQL.

How do I use SSDT with VS2015

I am using Windows 7 SP1.
I have SQL Server 2012 installed along with Visual Studio Community 2015.
The SQL Server 2012 installation has always forced me to use VS2010 Shell to launch SQL Server Data Tools.
I recently installed an update through the NuGet Package Manager in VS2015 which included SSDT. I was hoping that this would enable me to use SSDT with VS2015. However it still launches with VS2010.
My question is: How do I used SQL Server Data Tools with Visual Studio 2015?
Thanks
The latest release (Feb 2016) is the first release of SSDT that can target different versions of SSIS so you can now target 2012 from visual studio 2015:
https://blogs.msdn.microsoft.com/ssdt/2016/03/07/ssdt-preview-update-feb-2016/
It is still in preview though so you will need to download the pre-release bits:
https://msdn.microsoft.com/en-us/library/mt204009.aspx
or wait a month or so for the RTM release.
I usually use the pre-release builds and they are normally pretty solid but each environment is different :)
ed