ssdt

By all accounts, the introduction of SQL Server Data Tools (SSDT) in SQL Server 2012 was a watershed moment for many SQL Server developers. For better or for worse, SSDT as an IDE for business intelligence development changed – amongst other things – the way we deployed our SSIS packages (i.e. package vs project deployments), simplified Tabular Model development, and also introduced us to the SSISDB. Likewise the replacement of Business Intelligence Development Studio (BIDS) with SSDT had its detractors who were noticeably not very happy that in addition to installing SQL Server 2012 you still had to do a separate download and installation of BI templates for SSDT (previously, BI templates in BIDS were available as soon as you installed SQL Server 2005/2008). Although SSDT-BI is still being offered as a separate installation, subsequent releases of SSDT have included several enhancements changes that should go a long way to winning the hearts of its critics. In this article we conduct a comparative analysis of all versions (up until 16.5) of SSDT and identify all the major improvements that have been introduced in the BI templates.

众所周知，SQL Server 2012中SQL Server数据工具（SSDT）的引入是许多SQL Server开发人员的分水岭。 不管是好是坏，SSDT作为用于商务智能开发的IDE，改变了我们部署SSIS程序包（即程序包与项目的部署），简化表格格式开发的方式，并向我们介绍了SSISDB。 同样，用SSDT取代Business Intelligence Development Studio（BIDS）的反对者显然不满意，除了安装SQL Server 2012外，您还必须单独下载和安装SSDT的BI模板（以前是BI模板）安装SQL Server 2005/2008以后，BIDS中的Windows就可以使用。 尽管SSDT-BI仍作为单独的安装提供，但SSDT的后续发行版中包含一些增强功能更改，应该在赢得批评家的心中大有帮助。 在本文中，我们对SSDT的所有版本（直到16.5）进行了比较分析，并确定了BI模板中引入的所有主要改进。

适用于Visual Studio 2010的SSDT (SSDT for Visual Studio 2010)

The focus of the initial release of SSDT was designed to replace BIDS as well as VSDB, as shown in Table 1.

如表1所示，SSDT初始版本的重点是取代BIDS和VSDB。

As shown in Figure 1, the initial release of SSDT ran off a Visual Studio 2010 Shell and there were no major changes to the templates that were last released as part of BIDS 2008 except for the inclusion of Analysis Services Tabular Project template.

如图1所示，SSDT的初始版本运行于Visual Studio 2010 Shell中，并且除了包含Analysis Services Tabular Project模板之外，对作为BIDS 2008的一部分最后发布的模板没有重大更改。

Although the initial release of SSDT contained almost similar templates to BIDS 2008, it did however provide several enhancements to those templates. For instance, for the first time ever we were introduced to the SSIS Toolbox window, and the SSIS (Integration Services) templates were enhanced to:

尽管SSDT的初始版本包含几乎与BIDS 2008相似的模板，但是它确实对这些模板提供了一些增强。 例如，我们第一次被引入SSIS工具箱窗口，并且SSIS（集成服务）模板增强了：

• Allow redo and undo of package changes 允许重做和撤消软件包更改
• In addition to variables, you could configure package parameters 除了变量之外，您还可以配置软件包参数
• Define project-wide connections that would be visible to all packages within a given project 定义整个项目范围内的连接，这些连接对于给定项目中的所有包都是可见的

适用于Visual Studio 2012的SSDT (SSDT for Visual Studio 2012)

SQL Server 2012 was released ahead of Visual Studio 2012 which explains why the initial release of SSDT ran off Visual Studio 2010. Later on, when Visual Studio 2012 was released, another version of SSDT that ran off Visual Studio 2012 was released. Except for changes in template icons shown in Figure 2, no new enhancements were done in the BI templates of SSDT 2012.

SQL Server 2012在Visual Studio 2012之前发布，这解释了为什么SSDT的初始版本要在Visual Studio 2010上发行。后来，当Visual Studio 2012发行时，又发行了从Visual Studio 2012上发行的另一个SSDT版本。 除了图2中显示的模板图标有所更改外，SSDT 2012的BI模板未进行任何新的增强。

适用于Visual Studio 2013的SSDT (SSDT for Visual Studio 2013)

A year after Visual Studio 2012 was released, Visual Studio 2013 was released yet at that time SQL Server 2012 was still the latest RTM version of SQL Server. Not surprisingly, as shown in Figure 3, the BI templates contained in SSDT 2013 were similar to its predecessor, SSDT 2012.

在Visual Studio 2012发布一年之后，Visual Studio 2013发布了，但那时SQL Server 2012仍然是SQL Server的最新RTM版本。 毫不奇怪， 如图3所示，SSDT 2013中包含的BI模板与其前身SSDT 2012类似。

适用于Visual Studio 2015的SSDT (SSDT for Visual Studio 2015)

The release of SQL Server 2016 introduced several enhancements relating to business intelligence templates, particularly the overwhelming changes in Reporting Services. As a result, the release of SSDT 2015 was expected to contain several enhancements to support SQL Server 2016 BI features.

SQL Server 2016的发行版引入了与商业智能模板有关的多项增强功能，特别是Reporting Services中的压倒性变化。 因此，SSDT 2015发行版有望包含一些增强功能以​​支持SQL Server 2016 BI功能。

1. SSAS表格模型资源管理器 (1. SSAS Tabular Model Explorer)

A noticeable improvement in the Analysis Services Tabular Project template was the inclusion of the Tabular Model Explorer, shown in Figure 4. Although, compared to multidimensional cubes, SSAS Tabular Models were easier to design and work with, configuration of the model.bim file was such that you had to navigate to different areas of Visual Studio to, i.e. identify total number of measures in the model, identify a list of existing configured data sources, etc. Fortunately, Tabular Model Explorer, reduces some of that navigation exercise by providing a collapsible tree structure of model.bim properties such as data sources, KPIs, list of tables, roles and measures.

Analysis Services表格项目模板中的显着改进是包含了表格模型资源管理器，如图4所示。 尽管与多维多维数据集相比，SSAS表格模型更易于设计和使用，但是model.bim文件的配置使您必须导航到Visual Studio的不同区域，例如，确定模型中的度量总数，幸运的是，表格模型资源管理器通过提供可折叠的model.bim属性树结构（例如数据源，KPI，表列表，角色和度量）来减少了一些导航工作。

Similarly to other Visual Studio windows such as Solution Explorer, Tabular Model Explorer has the following built-in functionality:

与其他Visual Studio窗口（例如解决方案资源管理器）类似，表格模型资源管理器具有以下内置功能：

• Sort contents of the model – by default, the explorer is sorted alphabetically 对模型内容进行排序–默认情况下，资源管理器按字母顺序排序
• Search within the model 在模型内搜索
• Reposition the window i.e. float, dock, hide etc. 重新定位窗口，即浮动，停靠，隐藏等。

Finally, you can only use Tabular Model Explorer against SQL Server 2016 Tabular Models or higher. That, means if you change your solution compatibility level to a level lower than 1200 as shown in Figure 5, you will run into an error returned in Figure 6.

最后，您只能针对SQL Server 2016表格模型或更高版本使用表格模型资源管理器。 这意味着，如果您将解决方案兼容性级别更改为低于1200的级别（ 如图5所示），则会遇到图6返回的错误。

2. SSRS可调参数窗格 (2. SSRS Adjustable Parameters Pane)

Perhaps one of the frustrating issues with SSRS parameters was its inability to reposition them according to your preference. Luckily, SQL Server 2016 introduced the ability to customise the position of report parameters. SSDT 2015 introduces a parameters grid that can be used to adjust the position and appearance of report parameters, as shown in Figure 7.

SSRS参数令人沮丧的问题之一是它无法根据您的喜好重新放置它们。 幸运的是，SQL Server 2016引入了自定义报表参数位置的功能。 SSDT 2015引入了一个参数网格，可用于调整报表参数的位置和外观， 如图7所示。

The easiest way to access the parameters grid is to right click on the report body region, select the View option, and then click on Parameters.

访问参数网格的最简单方法是右键单击报表正文区域，选择“ 查看”选项，然后单击“ 参数” 。

3. SSIS单包部署和新的Hadoop任务 (3. SSIS Single Package Deployment & new Hadoop Tasks)

In spite of the benefits, one limitation of project deployment in SSIS was that the Deploy option was only available at the project level. That meant even if you made changes to a single package in a project, you still had to redeploy the entire project. Luckily, SQL Server 2016 supports deployment of a single package and SSDT 2015 provides support for single package deployment through the Deploy Package option shown in Figure 8.

尽管有这些好处，但SSIS中项目部署的局限性在于“ 部署”选项仅在项目级别可用。 这意味着即使您对项目中的单个程序包进行了更改，也仍然必须重新部署整个项目。 幸运的是，SQL Server 2016支持单个程序包的部署，SSDT 2015通过图8所示的Deploy Package选项提供对单个程序包部署的支持。

The Integration Services Project template in SSDT 2015 further includes components that can be used to configure tasks relating to Hadoop. The 3 Hadoop-related tasks are shown in Figure 9.

SSDT 2015中的Integration Services Project模板进一步包含可用于配置与Hadoop相关的任务的组件。 这三个与Hadoop相关的任务如图9所示。

One of the improvements in SSDT 2015 was its support for Azure ETL development. As a result, Microsoft released a separate installation file, Azure Feature Pack for Integration Services (SSIS) that makes it possible for SSIS to connect, process and transfer data between Azure and on-premises data sources. A list of available Azure ETL tasks are shown in Figure 10.

SSDT 2015的改进之一是对Azure ETL开发的支持。 因此，Microsoft发布了一个单独的安装文件，即用于集成服务的Azure功能包（SSIS） ，使SSIS可以在Azure和本地数据源之间连接，处理和传输数据。 可用的Azure ETL任务列表如图10所示。

We conclude the review of SSDT 2015 by mentioning another exciting feature introduced in the Integrations Services Project template, the Package Parts. Package Parts allows developers to setup package template that can be executed within a control flow area.

通过提及Integrations Services项目模板模板中的另一个令人兴奋的功能，即Package Parts ，我们结束了SSDT 2015的回顾。 打包部件允许开发人员设置可以在控制流区域内执行的打包模板。

参考资料 (References)

• How to use Package Parts to develop easily maintainable Data Warehouse solutions 如何使用包装零件来开发易于维护的数据仓库解决方案
• Previous releases of SQL Server Data Tools (SSDT and SSDT-BI) SQL Server数据工具的早期版本（SSDT和SSDT-BI）
• Business Intelligence Development Studio 商业智能开发工作室
• SQL Server Data Tools: A Work in Progress SQL Server数据工具：正在进行中

翻译自: https://www.sqlshack.com/the-evolution-of-sql-server-data-tools-ssdt-for-business-intelligence-development/

ssdt