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)
Related
Our current Azure build agents are using a windows-2019 VM-image and that includes VS2019 and SQL LocalDb 2016.
We're wanting to use a more recent version of SQL LocalDb and I'm trying to find out which version of SQL Localdb ships with VS 2022.
Nothing is mentioned in the Azure hosted agents page or related included software link for windows-latest/windows-2022.
SELECT ##Version from a windows-latest image returns:
Microsoft SQL Server 2019 (RTM-CU12) (KB5004524) - 15.0.4153.1 (X64)
Jul 19 2021 15:37:34
Copyright (C) 2019 Microsoft Corporation
Express Edition (64-bit) on Windows Server 2022 Datacenter 10.0 (Build 20348: ) (Hypervisor)
When deploying an SSIS package I get the following error:
This package works on my visual studio. This might be a dumb question, but do I need to install something on the server where the SISS catalog is deployed?
I'm using a "Oracle Source" connection, which I think is the connection manager giving the issue.
the package is running in 64 bits (in 32 bits also fails with the same error)
it seems the error is that it doesn't recognise the connection manager
the package was developed in VisualStudio 2019 (with a target version 2019 in the properties)
My SQL server database is Microsoft SQL Server 2014 - 12.0.2548.0 (X64) Jun 8 2015 11:08:03 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)
and my Oracle db is Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
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
The SQL Server version I'm running is 2012 (11.0.3153) in our dev environment..
I've just applied SQL Server SP2 to my database but the version appears unchanged. I need the version level at 11.0.5058 to match our production.
There was no errors during the installation.
Any idea what's going on?
Select ##version shows:
Microsoft SQL Server 2012 (SP1) - 11.0.3153.0 (Intel X86)
Jul 22 2014 15:41:01
Copyright (c) Microsoft Corporation
Standard Edition on Windows NT 6.2 (Build 9200: ) (WOW64) (Hypervisor)
However I tried applying the patch again and I get this:
Upgrade Status: Installed.
There's not supposed to be a need for a restart but I'm doing that anyway.
Restart did not work either.
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.