we have SQL Server 2012 and Visual Studio 2013.
I needed to install BIDS (or SSDT) for developing reports.
I downloaded and installed Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013:
http://www.microsoft.com/en-us/download/details.aspx?id=42313
However during the installation I noticed that it runs SQL Server 2014 setup.
Why doesnt it ask for wich SQL Server version I need SSDT to be installed?
Will it work with SQL Server 2012?
Thanks.
If you use Visual Studio 2015 + SSDT, you will have a full backwards compatible version of the BI toolset (2012 and up for SSIS, 2008 and up for other SSAS/SSRS and the relational DB tools). For previous versions of the BI suite, these were tied to specific SQL Server versions:
SSDT-BI for VS2013 -> SQL Server 2014 support
SSDT-BI for VS2012 -> SQL Server 2012 support
BIDS -> SQL Server 2008 support
The current recommendation is to use Visual Studio 2015 + SSDT as it receives regular updates & bug fixes, and is backwards compatible with no need to map to a specific SQL Server version. You can download SSDT here.
Related
Is it possible to open a SSIS solution using Microsoft's free tools (Visual Studio Team Explorer and SQL Server Data Tools) or does it require a full installation of Visual Studio?
I am trying to do so with just the free tools and am getting an error saying that "this versino of Visual Studio is unable to open the following projects" then another one saying the solution I have opened is under source control but not currently configured for integrated source control in visual studio.
We have other users who use the full version of Visual Studio 2017 and it works fine so I am wondering if this is just a limitation of the free products offered by Microsoft.
To edit SQL Server 2005 SSIS packages, you need Visual Studio 2005 and installation of Business Intelligence Designer Studio, BIDS. This required a license, developer edition was sufficient, to access the tooling.
SQL Server 2008 & SQL Server 2008 R2 would install into Visual Studio 2008. This too required a SQL Server license as the media only existed on the server media.
SQL Server 2012 would install into both Visual Studio 2010 and Visual Studio 2012. This was delivered in both physical media installations and downloadable tooling which was rebranded to SQL Server Data Tools- BI Edition, now just SQL Server Data Tools and the components were just licensed via click through agreement.
SQL Server 2014 installs into Visual Studio 2013 and was now only available through the download of SSDT.
SQL Server 2016 added a new twist into the mix. It installed into Visual Studio 2015 but it could now create/edit/target SQL Server 2012, 2014 and 2016 packages. This was huge as until this point, as a consultant I would have required 5 different versions of the "same" program on my machine. Now I'd only need 3.
SQL Server 2017 installs SSDT in both Visual Studio 2015 and Visual Studio 2017.
I assume SQL Server 2019 will similarly target VS 2017 and VS 109.
Across all of these versions, if you didn't have Visual Studio installed, the installer would install the Visual Studio shell on your machine so that the project templates would work.
Last I knew, neither Visual Studio Community Edition nor VS Code will work with the SSDT templates so be sure and open the correct product to work with SSIS projects (.dtproj)
The warning/error about "under source control but not currently configured" smells like something is awry with how you have the TFS hook installed but I can't comment on that.
Download and install SSDT 2017 for Visual Studio
You can verify the status of your SSDT installation for Visual Studio by going to the Help, About Microsoft Visual Studio menu and looking for "SQL Server Integration Services." With ... 2017? you can now do a piecemeal install and only pick SQL Server Data Tools (database projects) or SSAS/SSIS/SSRS. Previously, the SSDT-BI install was trio of SS_S and SSDT (no BI) was the database projects.
Previous answer on where SSDT-BI is
You have at lease two options:
Use Visual Studio Community Edition together with SSDT. Still, you have to check its License terms with your Legal department - it might be not legal to use Community Edition in Enterprise.
Use Visual Studio Isolated Shell together with SSDT. More instructions on how to install it. As far as I know, it is legal to use it for debugging.
The VS Isolated Shell is usually installed with SQL Server 2014/16.
We have Visual Studio 2010 with .Net Framework 4.5
and SQL Server version 2008.
We are in the process of migrating SQL Serer 2008 to 2014.
I want to know the steps to migrate to 2014 and is there any settings or extensions or updates to be done for Visual Studio to make it compatible with SQL Server 2014?
For full support of SQL Server 2014 inside Visual Studio, you need to run at least Visual Studio 2012 and have SSDT installed as outlined here.
However, to connect to SQL Server from your application or from Visual Studio and to do basic operations against the database no update to Visual Studio 2010 is required.
I am preparing to do some web development against a SQL Server 2012 server on a fresh install of win 7 x64 development VM.
What should I install first, visual studio or SSMS?
This is my favorite order:
Windows update before installing anything.
SQL Server 2012
If you have SP1 integrated with you ISO file, skip to step 4.
If you have both SP1 and U5 integrated with your ISO file, skip to step 5
Unselect SQL Server Data Tools during installation (step 8 will install the VS 2012 templates instead of these old 2010 ones)
SQL Server 2012 SP1
SQL Server 2012 SP1 U5
Visual Studio 2012
If you have U3 integrated with you ISO file, skip to step 7.
Unselect SQL Server Data Tools during installation because we'll install the updated bits in step 7
Visual Studio 2012 U3
SQL Server Data Tools - BI (adds BI project templates to Visual Studio 2012)
SQL Server Data Tools (allows you to manage SQL Server 2012 from within visual Studio 2012)
Windows Update
ReSharper
StyleCop
SQL ToolBelt
Neither - you can install them in any order. While you do get the occasional question about it in various different forums, I have done this and never had an issue.
SQL does have a Visual Studio dependency (formerly) called BIDS, but Visual Studio can install over/around this no problem.
Note that this answer is correct when using the initial SQL 2012 release (as that was the latest edition when this question was asked). Subsequent releases may have changed things. I have made this answer CW to encourage others to edit it as necessary to include info about later versions.
I don't know if there is a different way for VMs but on Windows we used to install SQL Server first, as some of the configurations of Visual studio conflict with SQL Server configurations if it was installed before
No direct dependencies found between the two components, installing Visual Studio first then ensure that .NET Framework installed properly is my approach, then installing SQL Server, but in all cases the SQL Server installation installs the following software components - 2008:
NET Framework 3.5
SQL Server Native Client
SQL Server Setup support files
My approach:
Visual Studio 2008.
Visual Studio SP1.
SQL Server 2008.
Run Windows updates.
Useful question here
A couple of months ago, I uninstalled Business Logic from my machine as I did not need it. Now I want to work on some reporting, but I am unable to find the Business intelligence tool in my Visual Studio 2010 install.
How can I download and load it up into Visual Studio 2010 or SSMS for use please?
BIDS (SQL Server 2008/2008 R2) and SQL Server Data Tools (SQL Server 2012) are both part of the SQL Server installer (not Express Edition), not Visual Studio.
If you're using SQL Server 2008/08 R2, the Business Intelligence tools will be installed in a separate "version" of Visual Studio, which uses the Visual Studio 2008 shell. This means that if you're running VS 2010, you'll actually appear to have 2 versions of VS installed, VS 2010 for all your normal dev and VS 2008, which will contain the BI project types only).
If it's SQL Server 2012 that you're using, the BI project types will be installed using the VS 2010 shell, so they'll be accessible when you boot up VS 2010.
Run through your SQL Server installation process and choose the relevant BI components (Analysis Services/Reporting Services/Integration Services) on the "Feature Installation" step of the installation wizard.
I know there is an Issue using SQL Server 2000 Reporting Services and Visual Studio 2005, but does this error still exsist with Visual Studio 2008 and 2010?
If so, is there any work-aground to get this working?
I do know that SSIS 2005 requires VS 2005 and that SSIS 2008 requires VS 2008. So if you have upgraded your SQL Server 2005 client tool installation to 2008, there is no way (AFAIK) to create SSIS 2005 projects.
My guess is that you will see the same issues with SSRS as with SSIS.