SQL Server Data Tools – Business Intelligence for Visual Studio 2012 released online

SQL Server Data Tools – Business Intelligence for Visual Studio 2012 released online

Rate This
  • Comments 43

Today we are releasing SQL Server Data Tools – Business Intelligence for Visual Studio 2012 (SSDT BI) templates. With SSDT BI for Visual Studio 2012 you can develop and deploy SQL Server Business intelligence projects. Projects created in Visual Studio 2010 can be opened in Visual Studio 2012 and the other way around without upgrading or downgrading – it just works.

The download/install is named to ensure you get the SSDT templates that contain the Business Intelligence projects. The setup for these tools is now available from the web and can be downloaded in multiple languages right here: http://www.microsoft.com/download/details.aspx?id=36843

The setup includes:

  • Visual Studio 2012 integrated shell (if you
    don’t have Visual Studio 2012 on your machine)
  • Project templates for
    • Analysis services projects
    • Reporting services projects
    • Integration services projects


 It will be installed as a new shared feature for SQL Server 2012 and can be uninstalled from there.

This download contains the same features as SQL Server 2012 SP1 and supports the themes introduced for Visual Studio 2012.

Some screenshots of the templates in Visual Studio 2012:

New project in Visual Studio 2012 black theme

Multi-dimensional project in Visual Studio 2012 light theme

Tabular model project in Visual Studio 2012 dark theme

Integration services project in Visual Studio 2012 dark theme

Reporting services project in Visual Studio 2012 light theme

Happy developing!

Leave a Comment
  • Please add 6 and 3 and type the answer here:
  • Post
  • Although the installer claims it supports 32 and 64 bits, I was unable to install it with my existing 64 bit SQL Server 2012 installation!

  • should the setup really work on a 64-bit system with a 64-bit SQL Server 2012 installed?

    the setup is only 32-bit as Visual Studio 2012 (Shell) is 32-bit only but it tries to install 32-bit version of SP1 for SQL Server 2012 which fails and therefore installation is not possible.

    Why is the SP1 included in the setup and why does it not detect it correctly that SP1 is already installed on 64-bit SQL Server ?

  • will the BI templates for VS2012 included in the next release SSDT ?

    SSDT for VS2010 includes all templates while SSDT for VS2012 does not include the BI template and those must be installed separately.

    Or will SSDT for VS2010 split into two separate setups for SQL Server database projects and for BI projects like it is now with VS2012 ?

  • Setup failure on existing 64 bit SQL Server 2012 installation:

    ------------------------------

    SQL Server Setup has encountered the following error:

    Value cannot be null.

    Parameter name: doc.

    For help, click: go.microsoft.com/fwlink

  • I have had Success installing with existing SQL 2012. Given visual studio is 32 bit I choose new install and completed ok , also SQL 2012 was already at SP1. with  SSDT shell was already.

  • For those having issues it seems you need to choose the "perform new install" instead of "add features to existing. "

    This seems to get around the 32/64 bit issue. Your only option is The Sql server Data Tools Business Intelligence so its not like it is doing a new install of sql

  • Thanks, but "perform new install" gives me the same error. My existing SQL 2012 BI is already at SP1, and I'm running the setup as Administrator.

  • This is a great step forward for developers targeting SQL 2012. Now, when can we expect Visual Studio 2012 to have some sort of support for .ssmssln and .ssmsproj templates?

  • "Setup failure on existing 64 bit SQL Server 2012 installation:

    ------------------------------

    SQL Server Setup has encountered the following error:

    Value cannot be null.

    Parameter name: doc."

    @RS

    have you installed Visual Studio 2012 or Visual Studio 2012Shell on this computer and all required prerequisite as mentioned on the download page ?

  • @Kevin:

    "This is a great step forward for developers targeting SQL 2012. Now, when can we expect Visual Studio 2012 to have some sort of support for .ssmssln and .ssmsproj templates?"

    SSMS 2012 is a Visual Studio 2012 Shell.

    As such I would expect VS2012 should be able to open .ssmssln and .ssmsproj - have you tried it and what error do you get ?

  • Yes you need to select "perform new install".

    @Daniel SSDT for BI for VS 2010 is part of the SQL installation. SSDT for BI will not become part of the Visual studio setup like SSDT for SQL is.

    @Kevin you will need to install our setup manually to install our templates that support  .ssmssln and .ssmsproj

    @Daniel, VS 2012 will be installed for you if you don't have it on your machine, if you do then we will not install the shell.

    Please file any problems and issues at connect.microsoft.com/sqlserver

  • @Daniel - I just get an xml editor for the ssmssln or ssmsproj

    @Kasper - how would I go about installing the setup manually?

  • @Kevin in order for Visual Studio 2012 to understand the .ssmssln and .ssmsproj projects you need to install the templates. These templates get installed by the setup mentioned in the blog post above. These will not be understood by Visual Studio 2012 without installing our setup.

    Hope that helps

  • @Kasper - I have downloaded and installed the only setup file I see referenced in the blog post above. I can open, edit, and execute the various BI project types in VS2012 just fine. However, the setup above does not appear to add any support to VS 2012 for SSMS solution/project files. I hadn't assumed that those types of files WOULD be supported, as nothing regarding SSMS is mentioned above. Are you saying that the above install for SSDT-BI should add support for SSMS solution/project files?

  • If you get the error Rule "Same architecture installation" failed.

    The CPU architecture of installing feature(s) is different than the instance specified. To continue, add features to this instance with the same architecture.

    The problem could happen when you choose the option "add features to an existing installation of SQL Server 2012"

    The probable resolution is to choose the other option during the setup which says "Perform a new installation of SQL Server 2012" (default choice). You will only need to check the one new shared feature  "SQL Server Data Tools – Business Intelligence for Visual Studio 2012" and you will not have to install a new instance of SQL Server 2012.

Page 1 of 3 (43 items) 123