Skip to main content

Where is my BI Development Tool?

DontPanic

"The development tool for SQL Server business intelligence packages is missing!" says almost every developer who installs SQL Server 2014. It's okay, don't panic.  Microsoft decided to separate the installer for the server and the installer for the development environment.  Unfortunately, the next statement by almost every developer who installs SQL Server 2014 is "There are MULTIPLE SQL Server Data Tools?!?".  Also not a problem, let's talk about the difference options and how to get the correct software on your machine.

Option 1 is SQL Server Data Tools (the original), which is a template for Visual Studio that allows you to create and store information on databases and database objects.  This tool is part of Visual Studio.  For more information, see: http://msdn.microsoft.com/en-us/data/hh297027.

Option 2/3 are SQL Server Data Tools - Business Intelligence, which contain the templates for SSIS, SSAS, and SSRS (the standard BI tools we are accustomed to). This tool is part of SQL Server.  You have two places to download this (depending on if you're developing for SSIS 2012 or SSIS 2014.  Here are those download links:

  1. Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012 (and SSIS 2012): http://www.microsoft.com/en-us/download/details.aspx?id=36843
  2. Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013 (and SSIS 2014): http://www.microsoft.com/en-us/download/details.aspx?id=42313

I do wonder why they are named the same.  Is it possible that Microsoft might merge these two products in the future?  This could be a great move for full data warehouse projects - designing your data layer and then populating it with ETL go hand-in-hand!  Pretty please?

Labels:

Comments

Unknown said…
Hi Jessica,

Were you able to fix this problem? I'm having the same issue where I cannot create SSIS packages in VS 2013
October 2, 2014 at 11:42 AM
Jessica M. Moss said…
Hi Freddy,

To create SSIS packages, you need to download SSDT - BI, with the links in the above post.

Good luck!
Jessica
October 12, 2014 at 7:21 AM
Unknown said…
I did and install it. But the templates wont show up on the new project menu
October 12, 2014 at 7:23 AM
Jessica M. Moss said…
Sorry Freddy,

Installing the templates should work... If uninstalling and reinstalling both Visual Studio and SSDT-BI templates doesn't fix the problem, you may need to contact Microsoft support.

Jessica
October 12, 2014 at 7:30 AM
Post a Comment

Popular posts from this blog

SSIS Configuration to Configuration to Configuration Schema

I've gotten several requests to put down in writing the configuration schema that I use as the base of my SQL Server Integration Services framework. It contains a set of configurations: an indirect environment variable configuration, which points to an XML configuration file configuration, which points to a SQL Server configuration. I learned this configuration from the Project REAL Reference Implementation . If you're getting started with a BI implementation, I highly recommend that you download it for some great ideas and best practices. Steps to implement: 1) Create an environment variable on your machine with the name of SSIS_CONFIG_FILE and the value of: C:\SSIS\Config\MasterConfigFile.dtsConfig. 2) Create an SSIS configuration file at C:\ SSIS\Config\MasterConfigFile.dtsConfig with the line: <configuration valuetype="String" path="\Package.Connections[CONFIG_SERVER].Properties[ConnectionString]" configuredtype="Property"><configuredv
29 comments
Read more

Execute SQL Task Designer Limit

After migrating a package from DTS to SSIS, I had a problem with an Execute SQL Task. I couldn't change any characters in the SQLStatement property; I couldn't add any new characters; I could delete characters, but not retype them! After googling several variations of "integration services" "read only" and "Execute SQL Task", I deleted about half of the entry in a fit of frustration. Lo and behold, I could type again. Apparently, there is limit on the size or number of characters that can be entered in the SQLStatement property. From my experimentation, I came up with a limit of 32767 characters. The interesting thing is that the restriction only seems to be on the designer. If you set the SourceType to "Variable" and use a variable that contains more than 32767 characters, the task will execute. Also, if you use the "Direct Input" SourceType and modify the package XML to set the SQLStatement longer than 32767 characters,
10 comments
Read more

Reporting Services 2008 Configuration Mistake

To start working with the management side of SQL Server Reporting Services 2008, I decided to set up a report server and report manager. Unfortunately, I made a mistake while setting up my configuration that left me a little perplexed. Here are the steps I took to cause, track down, and solve the issue. Problem: I began by opening the Reporting Services Configuration Manager from the Start Menu. I clicked through each of the menu options and accepted the defaults for any question with a warning symbol, since warning symbol typically designate an action item. After two minutes, all of the warning symbols had disappeared, and I was ready to begin managing my report server. Unfortunately, opening up a browser and trying to open up the report manager resulted in the dreaded " The report server has encountered a configuration error. (rsServerConfigurationError) " message. Sherlock-ing it: I put on my sleuthing hat and went to the log file directory: C:\Program Files\Microsoft
47 comments
Read more