Does downgrading visual studio 2017 to 2015 affect code? - sql-server

I am using visual studio 2017 and sql server 2016 for development of SSIS. I am in situation where I want to deploy my SSIS package to client side where old visual studio 2015 is used. So because of this I am not able to deploy it. So my question is how do I deploy my SSIS package to client side? Does downgrading visual studio from 2017 to 2015 affect my code?

SSIS projects are the same, as long as you install the latest version of SSDT.
Deployment has nothing to do with Visual Studio though. You need to develop your SSIS project targeting the same version as the production server. Many features depend on the target server's version. For example, SSIS Package Parts can only be used for projects that target SQL Server 2016 and above.
I've been using both Visual Studio versions on the same project for almost a year because SSIS support in VS 2017 was only a preview until recently. I had to wait until October 2017 for SSIS in VS 2017 to became stable enough to ditch VS 2015. Up until August 2017 there was a nasty bug that didn't allow me to open C# transformation tasks in 2017, so I had to switch to 2015 each time I wanted to edit them.
As I remember, diffing the project files showed that the only change from one VS version to another was a different version number in the file.
There was no one-way project upgrade between 2015 and 2017.

Related

SSIS project Target Server Version changing unexpecteldy

We have SSIS project with Target version
We need to use this target version if someone need to load some data or for develop packages. We are using VS 2017 with latest patches. If someone try to change some package of project and deploy only this package into SSISDB then next opening of project in VS will show that now target server version 2019. All developers use VS 2017 only (double checked this). Why target version changing to 2019 ? We can't run this with target version 2019 because few times saw such problems like not full loading of data despite on green mark check after package completion and this happenig only with target version 2019 , everything is good when we changing target version back to 2017 and running the same packages. But this is difficult to control everyone to change target server version back to 2017 every time when someone just need to make some minor changes to some of package of the project.
Here are versions of our services
Microsoft SQL Server 2017 (RTM-CU22-GDR) (KB4583457) - 14.0.3370.1 (X64) Nov 6 2020 18:19:52 Copyright (C) 2017 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2019 Datacenter 10.0 (Build 17763: ) (Hypervisor)
Integration Services 14.0
Visual Studio Proffessional 2017 15.9.46
Just step by step what i'm doing :
Open my project in Visual Studio 2017 and check target server version
It is not comfortable for us due to strange behavior of Visual Studio when loading some data
Then im changing Target Server Version and Visual Studio Starts to modify every of my packages inside this project ( to translate this to English it says "converting of packages in progress" )
Now project has target version 2017 ( and per picture above every package got some changes due this target version changing ) I deploy this back to SSISDB
I open this project again in visual studio ( load from SSISDB everything that i deployed earlier ) and see
Then I open any of packages and just do minor changing inside , save this to current opened project in VS ( target server version still 2017 )
Then I deploy package to SSISDB (exacly package not project ) and i'm sure that this package was made with target version 2017.
Then I open my project again from SSISDB and now I see

SSDT vs SSDT-BI

What are the differences between SSDT and SSDT- Business Intelligence?
I've installed SQL Server 2017 and then proceeded to download Business Intelligence Development Studio but found out that it was replaced by SSDT/SSDT-BI (don't know the difference if there's any).
Do I need just SSDT or SSDT-BI? I can only find SSDT-BI for Visual Studio 2012 and 2013, not for VS 2017 while SSDT for VS 2017 is available.
Will this create any problems since I'm working with SQL Server 2017?
I'm a complete beginner at all this and this is only for a uni project. Please keep answers as simple as possible. Thank you very much.
There is only SSDT nowadays, which includes support for SQL Server Database, SSRS, SSRS, and SSIS projects. The download links are here. The current SSDT version (15.5.2 as of this writing) allows you to target SQL Azure Database, SQL Server 2017, as well as older versions so you don't need multiple versions of SSDT installed.
SSDT will install a minimal Visual Studio shell if VS is not already installed. If you already have VS installed, those project types will be added to the existing installation.
EDIT:
With Visual Studio 2019, SSDT for SQL Server database projects remains intregrated into the VS 2019 installer. Select the Data Storage and processing workload during install and choose SQL Server Data Tools. However, SAS, SSIS, and SSRS SSDT projects are now moved to separate Visual Studio extensions. These extensions can be manged post install from within Visual Studio under Extensions-->Manage Exentsions.
Yeah, this got a lot of people confused. According to this link (VS2012 & VS2013 timeframe):
SSDT is for building databases ONLY i.e. only base functionality.
SSDT-BI is for building SSIS/SSAS/SSRS solutions
But then it looks like from VS2015 onward they merged the two together into just SSDT, so after VS2013 there is no separate SSDT-BI install. I think.

SSIS 'Deploy' button disabled

I recently upgraded to Visual Studio 2017 and so SSDT for VS 2017 but then decided to go back to VS 2015 because of some other complication. I uninstalled SSDT for VS 2017 and installed SSDT for VS 2015. Now the Deploy button is disabled when I try to deploy my SSIS project. There are no messages saying why it's disabled. Not sure where to go from here. I tried to deploy the packages separately in SQL Server but because I have a project level parameter my packages uses so it's giving me an error.

SSRS missing in Visual Studio 2015 (community & enterprise trial version) template

I tried to solve my problem by using community and enterprise (trial) version of Visual Studio 2015. Couldn't solve it. Hope somebody can help me.
I want to generate a report by using SQL Server Reporting Services (SSRS). In some tutorial I see there are SSAS, SSRS & SSIS under templates | Business Intelligence when a new project is opened in Visual Studio. In my case, I don't see it as shown in the following picture:
If I check (my OS is Windows 10 64 bit) System Settings | System | App & features, I see SQL Server Data Tools 2015 is installed (strangely I have 2 SSDT) as seen in below.
I see similar problem (Missing Reporting Server templates in Visual Studio 2013 + Business Intelligence SSDT) for VS2013, in which the reporter has used 32 bit SSDT tools. Is this valid for VS2015 also? What I should do for VS2015?
I develop the SSRS and SSIS project in Visual studio 2012 and When i open it on visual Studio 2015. both project is not loaded. then I download the SSDT and updated Its start Working
I think this Link help You to find out Your Solution
ssdt bi for the visual studio 2015 stack over flow Answer
Install sql server enterprise or business intelligence ctp 3.3, install VS2015 professional and finally install the latest SSDT.
Uninstall previous SSDT installations.
Download SQL SERVER.
In Visual Studio go to Extensions and Updates and look for SQL SERVER DATA TOOLING. If the update doesn't appear, go to this page in the third point, download the setup for your regional settings.
If it doesn't work tell use what is the exact VS2015 version.

How do I put a SQL Server database under version control using Visual Studio Community 2015 RC?

I would like to put my database schema and its data in my git repository and have it version controlled, just like my code.
I have SQL Server 2008 R2 and Visual Studio Community 2015 RC. I know that Visual Studio 2010 upwards, Database project templates have been introduced to do just this. Please see this article for example. But I don't find those templates in my Visual Studio Community Edition 2015 RC installation.
Sticking to RC isn't very viable in the long term. Especially now, when Visual Studio 2015 RTM has been released.
Unless you have some really strong incentive to stay on Release Candidate, I would recommend to:
Get RTM Express Edition for free, whichever suits you best. SSDT 2015 is compatible with Web and Windows Desktop;
Get SSDT 2015 (again, for free) and install on top of that.
AFAIR, that should give you SQL Server database projects and everything else you might need. The only catch is that, as usual, it will be a somewhat longer route if you have ever had any CTP / RC versions installed on the same Windows instance before. Then again, it's nothing new.

Resources