I am trying to install tfs server 2015
OS - Server 2012
SQL - SQL server 2012 EXPRESS
There is an error
TF401159: The SQL Server instance you specified (server\SqlExpress) is
version 11.0.2100.60, which cannot be used in place or upgraded. For
more information about supported versions of SQL Server, visit
http://msdn.microsoft.com/library/dd578592(v=vs.120).aspx
how can I fix it ?
Do you have SP1 installed for SQL Express?
https://www.visualstudio.com/en-us/docs/setup-admin/requirements
https://www.microsoft.com/en-us/download/details.aspx?id=35579
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 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?
I've installed SQL Server 2016 Developer Edition, because Microsoft states:
SSDT database projects in Visual Studio 2017 currently support up to SQL Server 2016. Support for SQL Server 2017 will be coming soon in a Visual Studio 2017 update.
My question is: Should I install exclusively SSMS 2016 or SQL Server Management Studio 17.1 is compatible with SQL Server 2016 Developer Edition as well ?
Thank you #scsimon for giving me an air of confidence.
I've installed SSMS 2017.1. It's compatible with SQL Server 2016, it works like a charm and, to be honest, it is much faster then SSMS 2016.
I just downloaded and installed Visual Studio 2015 Community but SQL Server Express did not install with it - why?
Before I installed VS 2015 Update 1 and everything was perfect but now SQL Server Express did not get installed.
What is wrong ?
You have to install SQL server individually. visual studio package never have SQL server with them.
You can download SQL SERVER 2012 Express: https://www.microsoft.com/en-pk/download/details.aspx?id=29062
Download SQL Server Data Tools for Visual Studio 2015 to build SQL Server relational databases, Azure SQL databases, Integration Services packages, Analysis Services data models, and Reporting Services reports.
https://msdn.microsoft.com/en-us/library/mt204009.aspx
I´m trying to run an SSIS 2013 Package in SQL Server 2014 but i keep getting the error "package migration from version 8 to version 6 failed with error".
So i ckecked the vertion in SQL Server 2014 using a T-SQL query:
SELECT ##VERSION
and i got:
"Microsoft SQL Server 2012 (SP1) - 11.0.3153.0 (X64)
Jul 22 2014 15:26:36
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)
"
The response for this query should be SQL Server 2014, right?
What should i do to alter this?
This has nothing to do with running the package. I ran into the same error. What happened was that the package was deployed to an Integration services server (version 2012) using the 2014 IS wizard (or visual studio 2013 SSDT)... SSIS and Visual Studio 2013 will not work for SQL Server 2012. There are several Microsoft connect tickets for this but I doubt any of them will get fixed.
SSIS versions are not backwards compatible.
VS 2013 is used for SQL Server 2014, VS 2010/12 is used for SQL Server 2012.
So the SSIS modules created with VS2013 are only compatible to SQL Server 2014.
Older SQL Server versions (2012, 2008...) can not handle them.