I have 2 TFS Servers, one running TFS 2012 and another 2013. I have to move one collection from the 2012 to the 2013 version, but when I backup and restore it in the appropriate SQL server and click on the Attach Collection button, the TFS says that it can't find any databases (project collections) to attach.
What steps do I need to take to upgrade this database to the newer version without interfering with the continuous work of the server?
An attach upgrade is not recommended and is far more risky than an instance upgrade. You should upgrade your TFS 2012 to TFS 2013 first and then move the collection by detaching it first. Without the detach the database week not be listed.
You can, accepting the risk, detach the 2012 database from TFS, then backup and restore the detached 2012. When you attach the system will perform an upgrade.
You have to detach the collection from TFS2012, backup the SQL database from SQL Server of TFS2012, restore the database to SQL Server of TFS2013 then attach the collection on TFS2013.
Related
I have multiple Azure SQL databases. One database holds all the staging table and the other database holds all the fact/dim tables. Now in my development environment I have stored procedure which reads data from staging tables (from staging database) and loads the data into its respective fact/dim tables (in a different database).
The above scenario is all working fine. I have multiple SQL projects for each database.
Now how do I deploy the elastic database queries while deploying the dacpac?
Below is the error when I add the elastic queries as a part of my post deployment scripts in Visual studio and try to build it.
PS: The SQL project properties is set to target the V12 version of the Azure SQL Database
Which version of the SQL Server Data Tools (SSDT) are you using? If you are not using the latest (14.0.60413.0), give it a try to upgrade SSDT: https://msdn.microsoft.com/en-US/mt429383. With that version, I am now successfully able to compile and publish database projects and dacpacs.
To successfully build, you will need to install the latest SSDT Preview which includes support for these objects from here. Support for the latest Azure SQL DB and SQL Server 2016 features is only available in the Preview for VS2013 at present, whereas for VS2015 the support was shipped in VS2015 Update 2. Once SQL Server 2016 goes GA (June 1, 2016) an RTM update will be pushed through the Visual Studio 2013 Extensions and Updates channel containing this support. That will ensure you get monthly updates with the latest changes again.
Note that even with the latest bits, if you open the file itself you'll get an issue with the Intellisense parser. Building the project will work fine but on opening a document you will see the errors appear for that specific document. Note that the same issue occurs in SSMS when coding this into a query window. This is because the Intellisense parser is separate from the core build system. The fix for this is in progress and will land in a post-SQL Server 2016 update (likely late June - July timeframe).
Disclosure: I work on the SQL Server tools team.
We’re running TFS 2013 Update 1 and I’m planning an upgrade to TFS 2015 Update 1.
We have both SharePoint and Reporting Services installed and configured for TFS that I like to remove, because nobody ever uses them.
So, do I simply uncheck both Reporting and SharePoint during the TFS 2015 upgrade wizard. Is this the best way to do it?
Or, do I un-configure Sharepoint and Reporting Services first from our TFS 2013 installation? If so, what are the steps to do so?
Environment:
Server computer A:
Application tier for TFS 2013 Update 1
Data tier: SQL Server 2012 SP 1 for the TFS databases, and Reporting Services databases
Sharepoint services (only for TFS)
Server computer B:
SQL Server 2008 R2 hosting the SharePoint databases.
You can do either.
I'd probably uninstall/disable first if you're really sure you don't want them in the future (check with all the teams that they're not storing docs in SharePoint as they will lose them). That way the backup will be smaller/faster when you backup before you upgrade (Make sure you take a backup!!).
It's simple enough to do, just fire up the TFS Administration Console.
Select Reporting, Edit (this will stop the jobs) and uncheck "Use Reporting". Click OK.
For SharePoint, click SharePoint Web Applications and under the top section, click Modify against your server connection and choose Remove.
Make sure you take a new backup at this stage and then you can start the upgrade.
Some things to consider:
Are you sure you want to do this in-place? You could clone the server to new hardware and test the upgrade first or perform a migration upgrade. It means less downtime in the event of something going pear shaped.
If your collection(s) are large, this is likely going to take a long time. The 2015 upgrade seems to be slower than previous upgrades due to all the schema changes.
Are you sticking with a single server? That's fine, but you won't need server B for SharePoint so you could move to a dual server TFS install if capacity is a problem (You'd need to upgrade the SQL version on server B to act as a data tier though)
I'm a couple years late, but this still popped up in a search result so worth mentioning - use cmd prompt to do this:
Navigate to %programfiles%\Microsoft Team Foundation Server %#%\Tools\, and type TfsConfig.exe setup /uninstall:SharePointExtensions . This will "unconfigure" the feature in your App Tier.
Hi I need to move my source code from one my existing TFS server to a new TFS server that is a clone of my existing one. From what I remember I think both servers are 2012 and I am using Visual Studio 2013 for development.
The clone already has my project on it, but it is an old version of the code. The existing server has the latest code but will be decommissioned soon.
Without having admin access on either server how can I move my code from the existing server with the latest code to the new server with an old version of the code.
Is it possible to do this and maintain the project history including the last month of development, or will I only be able to keep the code ? TFS is a managed service for me and I don't have the option to stay on the existing server.
I have only seen solutions where the new TFS server is clean.
You need to use Team Foundation Server Integration Tool: https://visualstudiogallery.msdn.microsoft.com/eb77e739-c98c-4e36-9ead-fa115b27fefe
With this tool, you're able to migrate source code with history.
I'm trying to migrate our existing TFS 2008/SharePoint installation to TFS 2012/SharePoint 2010. If I do it without SharePoint it all works OK, but if I try and include SharePoint it fails.
At the moment I'm starting from scratch and including SharePoint.
I've run the Configure Extensions for SharePoint Products Wizard, restored the TFS 2008 databases, run STSADM from the command line, and now I'm attempting to run the TFS 2012 Upgrade Wizard: it fails at the, Configure the Server Running SharePoint step with the error "TF250004: The SharePoint Products installation is either corrupt or is not valid. Verify that SharePoint Products is a supported version and is functioning properly, and then try again."
Can someone please advise me what I've done wrong?
It seems that your TFS server can't detect you SharePoint .
Where is your Sharepoint server, is it running on the same computer with TFS server or on another machine?
With your upgrade ,did you change your hardware or use the same hardware as before.
Accroding to your description, you didn't mention whether you need to upgrade your SharePoint. You should finish SharePoint upgrade before your TFS server upgrade.And match TFS upgrade requirements https://msdn.microsoft.com/en-us/library/vstudio/dd631912(v=vs.120).aspx
You should also pay attention to your sharepoint permission.I suggest you use a "Full Permission" Account in sharepoint which interact with TFS .For your reference:http://social.msdn.microsoft.com/Forums/sr/tfsadmin/thread/ea2ef379-dd14-4e23-86e6-fbc156e430d8
I eventually unchecked the "Configure SharePoint Products for Use with Team Foundation Server" option to exclude SharePoint during the upgrade and then manually configured SharePoint after the upgrade, overcoming a host of problems along the way.
I am using Team foundation server 2021. I do take backup of all TFS databases regularly. So now in case of disaster recovery (in case full machine gets crash) how can i use this backup to recover TFS and all collection etc. I want easy and the best approach .
I have seen so many articles in microsoft website but nothing is really so helpful and difficult to understand. So please suggest a better tutorial or procedure to do it
I guess that you have TFS2012 Update 1 (there is no 2011 version). You should upgrade to TFS2012.2 which has the Scheduled Backups feature included.
When taking a backup of a running TFS instance always backup all databases. In cases of a disaster situation the only way to recover, is to restore all databases and re-run the TFS Application Tier install.
There is ample guidance available, plus the Backup tool that was introduced in the product with TFS 2012.2 is also available for older versions (2012 rtm and update 1) as part of the Team Foundation Power tools.
The guidance you should follow is that for either:
restore TFS to the same location (in case the server name for TFS and SQL remain teh same)
restore TFS to a new server (in case the server name for TFS or SQL has changed)