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.
Related
I have an issue because SQL Server Launchpad service does not start because SQL Server instance and Launchpad is different versions. How I could upgrade SQL Launchpad service?
When I download and start cummulative update it shows me SQL Server is version
Microsoft SQL Server 2019 (RTM-CU16-GDR) (KB5014353) - 15.0.4236.7 (X64) May 29 2022 15:55:47 Copyright (C) 2019 Microsoft Corporation Developer Edition (64-bit) on Windows 10 Pro 10.0 (Build 19044: ) (Hypervisor)
If I choose SQL Launchpad in update installation it also appear to be 15.0.4236.7
But in SQL Server Configuration manager it shows 15.0.2000.5
Is there any way to solve it? or only downgrade the SQL Server?
Thank you
First I installed SQL Server 2012 for learning. Because it doesn't take too much memory.
But later I need a SQL Server for development so I installed the latest version of SQL Server 2019 Developer edition.
After installation, I check the version of SQL Server in SSMS using
SELECT ##VERSION
and I get:
Microsoft SQL Server 2012 - 11.0.2100.60 (X64) Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200:)
I don't know how to fix this.
If you already had SQL Server 2012 installed, then the SQL Server 2019 Developer edition wasn't installed as the "default, unnamed" instance - since there can only ever be one of those.
So when you installed SQL Server 2019, you must have chosen an instance name - use that instance name when connecting, e.g. use .\INSTANCE or (local)\INSTANCE to connect to the new version of SQL Server installed
I have an SSIS project in VS:
Microsoft Visual Studio Professional 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Version 4.6.01590
SQL Server Data Tools 14.0.61116.0
Microsoft SQL Server Data Tools
SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 13.0.1601.5
Project > Properties > Configuration Properties > Deployment Target Version > TargetServerVersion = SQL Server 2016
I deployed and validated successfully on two SQL server instances, but cannot on a third.
The chief difference I see in the three instances is this:
First (success)
Microsoft SQL Server 2016 (RTM-GDR) (KB4019088) - 13.0.1742.0 (X64)
Jul 5 2017 23:41:17
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows Server 2012 R2 Datacenter 6.3 (Build 9600: ) (Hypervisor)
Second (success)
Microsoft SQL Server 2016 (RTM-GDR) (KB4019088) - 13.0.1742.0 (X64) Jul 5 2017 23:41:17 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows Server 2012 Datacenter 6.2 (Build 9200: ) (Hypervisor)
Third (failed)
Microsoft SQL Server 2016 (SP1-CU5) (KB4040714) - 13.0.4451.0 (X64) Sep 5 2017 16:12:34 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2012 R2 Datacenter 6.3 (Build 9600: ) (Hypervisor)
I have been unable to track down fixes for the errors via Google, and they seem to be the same as when I target SQL Server 2014. I can post those as an edit if necessary, but my suspicion is the Sql Server installation (perhaps an issue specific to the Enterprise edition or something otherwise missing from that install) and not my package based on the above.
Here are the first and likely most relevant errors:
I found that this error goes away if you deploy from within Visual Studio instead of the wizard that is output by the build. However, I don't think you can connect to remote SQL Server instances when deploying from Visual Studio (I think that a Windows login is required).
So the solution was to install SSDT (Visual Studio 2015) on the production machine and deploy locally. This is obviously not great because you then have to move the SSDT project to the target machine every time you want to deploy (i use Git for this).
I'm sure Microsoft will come up with a fix for this eventually... Although at the moment I'm still waiting for them to release SSDT for Visual Studio 2017.
=== EDIT October 2017
SSDT is now available in Visual Studio 2017. However, I found that I still had to deploy from a locally running Visual Studio (but I can't remember why since having tried this a couple months ago from VS2017)
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 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