How to install SQL Server support for Visual Studio 2017? - sql-server

I am not able to connect to SQL Server .dbml file. When I am trying to connect to SQL Server, it shows a message to "install the missing package". Now, when I am installing that missing plug-in, it just shows the progress bar and at last shows "Installation completed". But again when I try to connect, it shows the above error message.
Can anyone please help me to install it manually?
Step 1:
Step 2:
Step 3:

Search for and install the latest version of SSDT (Sql Server Data Tools).

I install Visual Studio (community edition) quite often and this happened to one of the PCs I develop on.
Uninstalling/Re-installing Visual Studio is what make this work.

Starting with Visual Studio 2017, the functionality of creating Database Projects has been integrated into the Visual Studio installation. There is no need to install the SSDT standalone installer for the core SSDT experience. To create Integration Services/Analysis Services/Reporting Services projects you still need the SSDT standalone installer.
For Database Projects, install the Data Storage and Processing workload for Visual Studio
For Analysis Services, Integration Services or Reporting Services projects, download and install SQL Server Data Tools

Related

How do I open a DTSX file in Visual Studio 2019?

How do I open a DTSX file for editing using Visual Studio 2019?
I have generated a DTSX file by using the Import Data wizard found in SQL Server Management Studio, using the same process outlined in this question. The answer to that question explains how to edit a .dtsx file, but it does not appear to be correct anymore. I am using Visual Studio 2019. The answer says I need to use this link to download SQL Server Data Tools for Visual Studio:
Download and install SQL Server Data Tools (SSDT) for Visual Studio
But at that link, it says:
Changes in SSDT for Visual Studio 2019
With Visual Studio 2019, the required functionality to enable Analysis Services,
Integration Services, and Reporting Services projects has moved into the
respective Visual Studio extensions. The core SSDT functionality to
create Database Projects has remained integral to Visual Studio (you
need to select the Data storage, and processing workload during
install). There's no more standalone SSDT installation required.
If you already have a license to Visual Studio 2019:
For SQL Database Projects, install the Data storage and Processing
workload for Visual Studio
For Analysis Services, Integration Services
or Reporting Services projects, install the appropriate extension(s)
from the marketplace
I believe I need Integration Services, but it doesn't have a link to the appropriate extension in the marketplace. Through various googling paths1, everything keeps pointing back to the SQL Server Integration Services Projects extension. I have installed this extension2, but I am still unable to open DSTX files.
Here's how I'm attempting to do it: In Visual Studio, am going to File|Open Project. Then I browse to the folder with the .dtsx file in it, change the filter to *.* (because .dtsx isn't in the list of supported project extensions), choose the file, and click Open. I get this message box:
So, my question again: How do I open a DSTX file from Visual Studio 2019?
See below for detailed versions and installed extensions.
1 For example, see Lesson 1-1: Create a new Integration Services project, where they create a DSTX project. The lesson's Prerequistes instructs you to install the SQL Server Data Tools from Download SQL Server Data Tools, which is the same link from above.
2 I note that version 3.1 of the extension is currently labeled a Preview and that release notes for this version includes the text, "This is the second preview release. We do not recommend using it for production." But I do not see where I am able to download an earlier version of this extension, either from the marketplace website or from in Visual Studio. I would try the latest production release if I could find it, but it doesn't seem to be available.
I also see there are two notes about issues with this preview release. Neither seem relevant to my situation. The first is a regression in VS 16.2 where they recommend upgrading to 16.2.3. I am already on 16.2.4. The second is an issue where the extension and/or Visual Studio Tools for Applications 2019 might be deleted during a VS instance upgrade. I have not done any upgrades to VS since installing this extension.
Installed Software
Visual Studio 2019, version 16.2.4
SQL Server Management Studio, version 17.9.1.
In Visual Studio, when I go to Help|About Microsoft Visual Studio, I also see the following listed in Installed Products (this list is not complete; it includes only the items that seemed relevant):
SQL Server Data Tools 16.0.61906.28070
SQL Server Integration Services 15.0.1301.433
In Visual Studio, when I go to Extensions|Manage Extensions, I see SQL Server Integration Services Projects in the list of installed extensions.
The error message indicates you are trying to open a project/solution. DTSX is a package.
You first need to open the .sln or .proj file. Within the project (solution explorer) you can open the dtsx. Do not try to open the dtsx file from the source control explorer as that does not open with the project references.
In summary, open the solution/project, then open the package from the solution explorer.
To edit and create integration services packages (.dtsx) is necessary to install SQL Server Integration Services Projects.
After installation Visual Studio 2019 can create or edit integration packages either independently (open file) or in Integration Services Project. It is also possible to open packages on SQL server even when SSMS fails with message:
Connecting to the Integration Services service on the computer "xxxx" failed with the following error: "Access is denied."
You will have to install SSMS, SSAS from VS Extensions> (In VS Menu, click "Extensions" and then "Manage Extensions

How does Visual Studio SSIS Handle Extensions and Package Deployment?

I'm fairly new to Visual Studio and SSIS and was wondering if someone could just clear up for me how Visual Studio SSIS Projects and Visual Studio in general handle Add-In Extension and Package Deployment.
The Scenario: I am currently developing and creating a Visual Studio SSIS Package on my local machine.I need to use an extension from the Tools > Extensions and Updates which just links me to a webpage.I need to install this and use it to make a package which I will deploy to the Integration Services Catalog on a SQL Server 2014 that does not have Visual Studio installed. When I deploy this project as a package will the things the extension did be baked into the package or is it like references where I will need to install the extension on the server that will be running the package via SQL Agent Job. Thanks, any help is appreciated.
When you deploy a package to the catalog, all libraries/extensions (eg.azure connection etc) are deployed along-with, so no special treatment is needed. But many a times you will need to ensure your frameworks( eg. .net 4.0 etc) exist for the extension to be executed on the integration services server you are deploying to.
In some cases you have to register the dlls using GACUtil, to the integration services server. Your custom tool installation instructions will specify that.

No SQL Server Data Tools in VS 2013 ultimate installed

I have no SQL Server Data Tool in Visual Studio 2013.
SSDT should be included in VS2013? Source
How can I install them?
I tried to install BI for VS 2013 but still don't have any SQL functions in VS.
Make sure Microsoft SQL Server Data Tools is checked when you install VS.
SQL tools like schema comparison are in SQL menu. SQL menu is not visible till any database project OR .scmp file OR file where its context is available is open.
For more details, refer:
http://pranavwithyou.wordpress.com/2013/09/20/schema-data-comparison-of-two-databases-with-visual-studio/
http://channel9.msdn.com/Events/Visual-Studio/Launch-2013/VS108
Update
Got this link on MSDN:
http://msdn.microsoft.com/en-us/data/hh297027
Download latest VS2013 Update 2 through extension update or by link http://www.visualstudio.com/downloads/download-visual-studio-vs
For SSDT-BI for VS 2013 install:
http://www.microsoft.com/en-us/download/details.aspx?id=42313
after installation restart Visual studio.
Lets hope, it should work then.
I don't have SQL menu, however I found it in Tools -> SQL Server

SSDT Not Working In Visual Studio 2010 SP1

I'm running Visual Studio 2010 SP1 Premium on Windows 7, and am trying to create SQL Server Reporting Services (SSRS) Reports. I've downloaded the new SQL Server Data Tools (SSDT) from http://msdn.microsoft.com/en-us/data/hh297027 and installed/restarted. If I go into VS Help->About, I can see "Microsoft SQL Server Data Tools 10.3.20225.0" in the list of installed products. However, SSDT doesn't seem to be showing up in the "New Project" window, and if I try to open existing SSRS 2005 reports projects (created in BIDS/VS 2005) it says "'Reports.rptproj' cannot be opened because its project type (.rptproj) is not supported by this version of the application. To open it, please use a version that supports this type of project".
Am I incorrect in my impression that VS/SSDT does not require SQL Server being installed? Is there some other software, package, or step that I'm missing in installing SSDT?
For SQL Server 2012 SSRS, the functionality of BIDS is REPLACED by SSDT. If you are working with SQL Server 2008 R2 (or earlier) SSRS, then you'll want to use BIDS from that version of SQL Server.
When you install SSDT, it includes templates for BI projects (i.e. SSAS, SSIS, SSRS). SSDT can be installed as a stand-alone application, or, if you have VS2010 SP1 on your machine, then SSDT will install inside of VS2010.
For the OLTP (including offline) database projects, there is NO template. Rather there is a new View named 'SQL Server Object Explorer'. For more about the latter, see my blog post.
The new project type is found under Other Languages->SQL Server-> SQL Sever Database Project.
Do not confuse that with the old to be deprecated projects under Database->SQL Server->Advanced
The BIDS part of SSDT is sort of a separate install. (although they've tried making it seem like one install.) See this on information about why one or the other might not be installed:
http://www.jamesserra.com/archive/2012/04/ssdt-installation-confusion/

Visual Studio and SQL Server - correct installation sequence?

I am rebuilding my development machine. This issue is not new to me, but I don't remember the solution.
I started with SQL 2008 Developer, then VS 2008 Pro, then the SQL SP1, then VS SP1. The result is that I cannot open SSIS projects (see the error below). What is the correct order so that I can avoid the installation of SQL Server Express and still have all the features working?
---------------------------
Microsoft Visual Studio
---------------------------
Package Load Failure
Package 'DataWarehouse VSIntegration layer' has failed to load properly ( GUID =
{4A0C6509-BF90-43DA-ABEE-0ABA3A8527F1} ). Please contact package vendor for
assistance. Application restart is recommended, due to possible environment
corruption. Would you like to disable loading this package in the future? You
may use 'devenv /resetskippkgs' to re-enable package loading.
---------------------------
Yes No
---------------------------
You should install SQL 2008 Developer first, this will rule out the need for VS installing SQL which comes with it. Or you could do like others suggested and choose custom VS installation.
My favorite way is this:
SQL 2008 Developer
Visual Studio Professional 2008
Run Windows Updates
Install Resharper :-)
Install RedGate SQL ToolBelt
But it seems that to get some features to work the proper order is:
Visual Studio Professional 2008 (with SQL Unchecked)
SQL 2008 Developer
Run Windows Updates
Install Resharper/Redgate Tools
Resharper and Redgate in my opinion are far the best tools for developing in C#/SQL.
It turns out I was missing 2 important pieces of information in my question that make this installation such a pain:
I was installing the 64 bit version of SQL Server
I was installing to a non-standard location (i.e. the D: drive, because C: is an SSD with not all
that much space)
This was not successful. Here is what I ended up doing in my first (second, and third) attempt:
Install VS 2008 Professional on D:
Install VS 2008 SP 1
Install SQL Server 2008 Developer Edition (instance and shared components on D:)
Install SQL Server SP 1
Apparently VS 2008 Pro does not require a database. I am not sure why I remembered that it does. While the Visual Studio installation was eventless, I encountered the following errors during the SQL Server installation:
The INSTANCESHAREDWOWDIR command line value was not specified.
I was able to resolve that be starting setup from the command line (thanks to this MSDN forum post):
setup.exe /INSTALLSHAREDWOWDIR="D:\Program Files(x86)\Microsoft SQL
Server" /INSTALLSHAREDDIR="D:\Program Files\Microsoft SQL Server"
/ACTION=install
Then towards the end of the installation, I got this error:
Upgrade Failed due to the following Error.The error code is :-2147467259.Message:Unspecified error
There is no solution, but a workaround, described in this post on connect.microsoft.com. It consists of copying a VS config file around before and after the installation, and re-running the installer just for BIDS (which is the one component that failed).
The SQL Server SP1 installation ran without issue. VS Studio, when trying to load a solution with an SSIS project, still threw the error that I posted in my original question.
I had ignored this error that popped up towards the end of the BIDS installation:
Microsoft Visual Studio Tools for Applications 2.0
Cannot find one or more components. Please reinstall the application.
However, there was no error in the install log and it completed "successfully", so I thought it would be ok to ignore the error.
It seems that my configuration is not possible (but I know with certainty that I had the 2005 versions of VS and SQL Server on a D: drive).
I uninstalled everything once again, manually deleted whatever folders were left, and reinstalled on the C: drive, including the SQL Server shared components. I put the instance folder on the D:.
Install VS 2008 Professional on C:
Install VS 2008 SP 1
Install SQL Server 2008 Developer Edition (instance on D:, shared components on C:)
Install SQL Server SP 1
This time everything installed and I can open my SSIS project.
If you are trying to install SQL-2008 and you also have visual studio 2008 installed with service pack one (SP1) and get the error
A previous release of Microsoft Visual Studio 2008 is installed on
this computer. Upgrade Microsoft Visual Studio 2008 to the SP1 before
installing SQL Server 2008”
Then welcome to the Microsoft beta testing program even if you purchased the faulty software.
With XP the most common solution seem to be renaming the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\VS\Servicing\9.0
and replacing 9.0 with 9.0Old. However this does not solve the problem if you are using windows 7 and the only solution I managed to find that worked was to uninstall VS2008 and all the components and to then install SQL-2008 and finally reinstall VS2008.
Install Visual Studio Professional 2008.
Install SQL 2008 Developer
Apply SQL SP1
Apply VS SP1
Then all should be good.

Resources