Which order should these be installed in? I have read in this SO post that VS2013 requires an update to work with SQL Server 2014.
It doesn't matter. The two products do not conflict and side-by-side installation is supported in any order.
After installing VS you'll need to then install the latest SSDT version for SQL Server 2014 support. SSDT is s component of Visual Studio, not SQL Server.
Related
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.
I have visual studio 2010 installed and working on my computer.
recently I have updated sql express 2008 to sql 2012. after visual studio prompted
"this server version is not supported. only servers up to Microsoft SQL
server 2008 are suported"
I have installed sql server data tools (from here https://msdn.microsoft.com/en-us/jj650014) to solve this problem, however unfortunately it keeps showing the message.
What am I doing wrong? How do I solve this?
Your best bet will be to install the latest version of SSDT from Microsoft. VS DB Projects stopped support with SQL 2008. SSDT for SQL 2010 stopped support w/ SQL 2012, I think. You don't need a license for the VS shell, though you might need to sign up w/ the MS developer program.
Go here for the SSDT blog: https://blogs.msdn.microsoft.com/ssdt/ You should see the most recent post or two pointing to the current release. This should support 2012+ without any issues. It will install the VS IDE if you don't have it installed.
FYI, the version you pointed to should work with SQL 2012, but you'd be better off using the latest version that is currently under active development. Ideally, the dacpac should be able to be used regardless of which version of SSDT you're using.
It might be worth checking to see what you're turning in. If you can turn in a script, it won't matter what version of SSDT you use. If you need to turn in the dacpac, you might have to double-check your install for SQL Express and SSDT to be sure they are the proper versions.
I've got VS2015 installed and the latest version of SQL Server Data Tools installed and can't seem to import a circa 2008 SSRS reporting project.
Or even create a new reporting project for that matter.
Can someone point me in the right direction?
Zack
As of Sep 14, 2015 Sql Server Reporting Services (SSRS) hasn't been released as part of SSDT 2015.
Link to the page.
One of the positive news from SSDT Preview update for August 2015 is now there will be only one installer for database and BI tools. No more SSDT naming confusion which was introduced with SQL Server 2012.
For now you have to install SSDT-BI-2013 or SSDT-BI-2012.
SSDT is updated on July 7 2016, can be downloaded from Microsoft website https://msdn.microsoft.com/en-us/library/mt204009.aspx
What version(s) of SQL Server Express are compatible with Visual Studio 2013 Professional edition? I have a machine with SQL Server Express 2008 R2 already installed - will VS2013 Professional work fine with that?
No!
If the version of SQL server is newer than the version of Visual Studio then you will get the message "This Version Not Supported" when you attempt to create a data connection
Yes. You can use newer version. But incase you already created a database in older version, you may need to migrate to new version.
SQL Server is the tool to manage database,Visual Studio 2013 is the tool to write code .net,visual...,the code connect to database by connectionString, so I think The Visual Studio 2013 work find in any SQL Server version
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