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

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.

Related

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.

Does downgrading visual studio 2017 to 2015 affect code?

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.

DTSX and SQL Server 2014

I am a freelancer. At a client's place, SQL Server is 2014, but the only DTSX tool is BIDS 9, which I would like to remove to install something a bit more up-to-date.
I am a bit confused by some pages telling that SSDT is for VS 2012 or 2013, and that SSDT and SSDT-BI are 2 different things.
So what should I install ? Can I use VS 2015 community + an extra package ?
I would be delighted to have the proper links, because I found MS site is also a bit confusing on the subject, and I would not like to make a mistake on this.
Thanks.
This page has a pretty clear description.
SSDT contains templates for building relational databases for the RDBMS and Azure SQL Database
SSDT-BI contains project templates for SSAS models, SSRS reports, and
SSIS packages.
There are two version of SSDT-BI. One for VS2012 and one for VS2013.
For SQL Server 2012 or 2014, you can use either SSDT-BI for Visual
Studio 2012 or SSDT-BI for Visual Studio 2013. The only difference is
between the two is the Visual Studio version.
You can use the download links on the page to get the right tools for the VS version that one plan on using.

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.

SQL Server 2014 CTP1 Setup failed

I have uninstalled Microsoft Visual Studio 2012 Ultimate and install VS professional 2013
after, i tried to Setup Sql Server 2014 but a message say
"Installation blocked due to detection of version of Visual Studio that install SQL Server 2012 client libraries.."
then i have uninstalled all Microsoft programs figured in this link without uninstalling visual studio 2013 .
and always i get the same problem
any solutions Please
At this point in time, you should be using CTP2, not CTP1.
You should be installing the CTP on a clean machine (preferably a VM), not a system with a bunch of pre-existing software - especially from previous versions of SQL Server / Visual Studio. CTP2 might get around this particular issue for you, but it's still best practice IMHO to run beta software in a clean environment.
Please review the release notes, in full, before proceeding.

Resources