I have a server that has TFS 2015. Originally, it was running against SQL Server 2012. I backed up the databases and then upgraded to SQL Server 2016. After upgrading to SQL Server 2016 TFS seems to work fine but I still see several entries in programs and features for SQL Server 2012.
My question: How do I check TFS 2015 to verify that it is indeed now running against SQL Server 2016?
If not, I'm guessing that if both SQL Server 2012 and 2016 are installed I have the ability to make TFS switch from one to the other?
Related
We are currently using TFS 2013 - Upgrade 2, connected to a SQL Server 2008 instance. We are trying to upgrade the TFS databases to a SQL Server 2014 instance (new server) with the databases being in 2008 compatibility. When trying the preview function of the TFSConfig RemapDBs command, we are getting the "TF246017 Team Foundation Server could not connect to the database" error. Is it potentially because TFS 2013 - Upgrade 2 doesn't support SQL Server 2014, despite the database being in a 2008 compatibility mode?
Thanks!
Is it potentially because TFS 2013 - Upgrade 2 doesn't support SQL Server 2014, despite the database being in a 2008 compatibility mode?
Shouldn't be. TFS 2013 Update 2 supports SQL Server 2014. See
https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=tfs-2013
I am using locally the MS SQL Server Management Studio 2012 with SQL server 2012 database engine.
I have the following question:
Can I upgrade ONLY the SQL Server Management Studio 2012 (TOOLS) to 2014 version, and leave my old 2012 already installed database engine version?
Yes, you can.
But install SSMS 2014 as standalone (instead of trying to upgrade tools).
From SSMS 2014 SP1 release notes you can see that it vitally supported SQL Server 2012. See how many compatibility fixes for 2012 were delivered.
Generally I'd recommend to prefer latest release of SSMS 2016 which
works with all supported versions of SQL Server (SQL Server 2008 - SQL Server 2016)
(Besides that I tried to find similar statement for SSMS 2014 (there was one), but I couldn't.)
I'm using SSMS 2008 + SSMS 2016 side by side and they are running just fine. In similar way, I was using SSMS 2008 + SSMS 2014 before the upgrade.
You can download and install SQL Server Management Studio using the links provided in: Scott Hanselman's website
There are links to various SSMS versions (2012, 2014, for x86, x64), as well as links to various SQL-Server Express versions.
By the way, you can use the latest SSMS 2014 to manage your 2012 database.
You could simply install new SSMS 2014 version and leave the 2012 version installed ONLY IF they are all 32-bit or 64-bit. You cannot upgrade 32-bit 2012 to 64-bit 2014 and vice versa. Ideally you could use 2014 version SSMS to access databases created in 2012 before because of the compatible level allows you to do that, but it will raise another problem for restoring the databases since you cannot restore any backup files that backed up from old(2012) to (2014) because of the database version did not match.
SSMS is now a separate free product that works with all versions from 2008 and up. The current version is 16.5.3
For older versions:
There is no explicit block for SQL Server 2000 or SQL Server 2005, but some features may not work properly.
You'll have to download the RC version if you want to connect to SQL Server vNext, eg to SQL Server on Linux
I tried to upgrade my mssql server from 2012 to 2014 but I ended up have two servers on my machine.
Now, whenever I connect to localhost it is always resolving to 2012 instance.
SQL Configuration manager 2014 also shows 2012 instance.
How can I change the default instance point to 2014 instead? and Are there any issues uninstalling 2012 version.
I am guessing from you question that you didn't do an "in-place" upgrade.
You can only have 1 SQL Server as the default instance, I believe the SQL Server installer will detect this automatically, and create a new instance for any subsequent installs.
If you absolutely have to have SQL Server 2014 as your default instance, you will need to uninstall SQL Server 2012 and re-install SQL Server 2014, or do an in-place upgrade of your SQL Server 2012.
We restored our TFS 2013 database backups on separate data tier with SQL Server 2012. Now I am trying to add these databases to TFS server (it's a sandpit tier), where I have a SQL Server 2008 R2 version. While running app tier wizard, I added SQL instance but it is throwing an error:
TF400860: the current version of following service is not supported registry Version 5, min version 5
Both servers have same version of TFS (TFS 2013.5)
Can anyone advise how to fix this?
The minimum SQL version for 2013 is SQL 2012 with SP1 https://www.visualstudio.com/en-us/docs/setup-admin/requirements
The minimum SQL server requirement for TFS 2013 is SQL server 2008 R2 (SP1).
The solution for this error is, we need to change the SQL server instance availability group as primary by logging in to same server
We have 4 data tiers, which are in sync, I tried it and I got it with SQL version 2008 R2. No need of SQL version 2012 or higher.
Thanks
Currently I am creating SSIS packages for SQL server 2014 using Visual Studio 2012 and the SSDTBI for VS2012.This works well.
But I found some compatability issues with VS2012 for SSIS 2014(on web).I'm new to SSIS.I dont know what is that exact issues with VS2012?.And also they mentioned SSIS 2014 is compatible only with VS2013.Here i have mentioned the link below.
http://www.stefanjohansson.org/2015/02/issues-upgrading-an-ssis-solutionpackage-from-visual-studio-2012-to-vs-2013/
http://blogs.technet.com/b/dataplatforminsider/archive/201
3/11/13/microsoft-sql-server-data-tools-update.aspx
Can anyone tell me what is exact compatability issues for VS2012 with SSIS 2014?.I can not seem to find anything on google.
Thank you
According to msdn it possible.
On an instance of SQL Server 2014, you can import packages from an
instance of SQL Server 2008 or from an instance of SQL Server 2012,
but you cannot export packages to an instance of SQL Server 2008 or to
an instance of SQL Server 2012.
-
Run packages. You can run SQL Server 2008 Integration Services and SQL
Server 2012 Integration Services packages by using the SQL Server 2014
version of the dtexec utility or of SQL Server Agent. Whenever a SQL
Server 2014 Integration Services tool loads a package that was
developed in SQL Server 2008 or SQL Server 2012, the tool temporarily
converts, in memory, the package to the package format that SQL Server
2014 Integration Services (SSIS) uses. If the SQL Server 2008 or SQL
Server 2012 package has issues that prevent a successful conversion,
the SQL Server 2014 Integration Services tool cannot run the package
until those issues are resolved. For more information, see Upgrade
Integration Services Packages.
However, I would just use VS 2013 if you can.