Is SSDTBI for Visual Studio 2012 Compatible with SQL Server 2014? - sql-server

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.

Related

Modify SSIS 2008 project -.dtsx

I have a development server with SQL server 2017 Developer edition and integration service,
There is a SSIS project (.dtproj) I believe it was built using 2008 BIDS, So I want to do some changes/modification on that,
Do I need to install SQL server 2008 R2 Integration Service? Or Can I do this by only using BIDS 2008? and is there any other software's that I need to install.
if you are using vs2017 then you need to install SQL Server Data Tools (SSDT)
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-ver15

SSIS Visual Studio 2019 for SQL Server 2008

The question is can I use Visual Studio 2019 with the most current SSIS to create SSIS packages for SQL Server 2008? Or do I need to download an earlier version of Visual Studio?
I do not have access yet to execute on the server I am waiting for this and just doing some research to get tools ready in the mean time. So I have not tried anything yet.
You have to install SQL Server Data Tools (SSDT) for Visual Studio 2019.
This is the link
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?redirectedfrom=MSDN&view=sql-server-ver15
Says that you can't.
Supported SQL versions
Integration Services packages SQL Server 2012 - SQL Server 2019
Unfortunately, SSIS 2008 is too old. Additionally, SQL Server 2008, and its SSIS, are out of support. I strongly suggest upgrading your SSIS to a later and supported version.
VS2019 supports SSIS development for the following SSIS versions:
2012
2014
2016
2017
2019
-- UPDATE --
can sql server2008 use ssis later than 2008? this is what i was trying
to establish
No, SQL Server version and SSIS version are one and the same.
-- UPDATE #2 --
BIDS (Business Intelligence Development Studio) can be found after installing the full version of SQL server 2008.
Check it out here: Creating a SSIS package in VS 2008

How to use SSIS of SQL Server 2014 on Windows 7

I'm trying to use SSIS of SQL Server 2014, I already had SQL Server so I've followed some tutorials of how to add the SSIS functionality. I downloaded the setup of SQL Server but SSIS is missing when I look for it.
I read on a previous post that it's because I'm downloading SQL Server express
https://www.microsoft.com/en-us/download/details.aspx?id=42299 and that version doesn't have that feature.
But I've seen videos where they have the same link and to them do appear the SSIS when they're doing the same procedure.
My question: what can I do to use SSIS of SQL Server because I have Windows 7 and other versions as SQL Server 2016, 2017 need Windows 8 or newer, but I don't want to install them.
You can download SQL Server Developer Edition, if you are just planning to use it for development purposes. It is having SSIS coming with it.
SQL Server Developer Edition 2014 supports Windows 7. You can see more details here
The SQL Server Developer Edition 2014 download instructions are available in the Stackoverflow post
You need to install Sql Server Developer Tools-BI (SSDT-BI) to work on Integration Services Project. You can download SSDT from here. Choose the one corresponding to SQL Server 2014.

Determine SQL Server instance being used by TFS 2015

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?

SQL Server 2008 SSIS package compatability

I am trying to save an SSIS package on a sql server running 2005. The issue I have is that I am using SQL Server Management Studio 2008 on my local machine to do this and it won't let me save the package in on the server because its not compatible with 2008.
Is their some kind of compatibility option in management studio that I don't know about?
The short answer is no: the 2005 and 2008 package formats are different, and 2008 packages can't be downgraded to 2005.
The best solution is probably just to install the 2005 tools alongside the 2008 ones and use them for designing your packages.

Resources