It’s not often that I write negative articles surrounding SQL Server’s latest release but ever since we upgraded one of our BI boxes to run SQL Server Reporting Services 2016 (SSRS 2016), I have picked up on some frustrations from my team when using the upgraded Report Manager portal due to the unavailability of features that used to exist in versions prior to SSRS 2016. I have since realized that in spite of the many exciting features and improvements introduced in SSRS 2016, there is a downside to this latest version of reporting services that is likely to leave many administrators frustrated.

我很少经常围绕SQL Server的最新版本撰写负面文章,但是自从我们升级了一个BI盒以运行SQL Server Reporting Services 2016(SSRS 2016)以来,使用升级后的Report时,我的团队就感到沮丧Manager门户网站由于无法提供SSRS 2016之前的版本中的功能。此后,我意识到,尽管SSRS 2016中引入了许多令人兴奋的功能和改进,但是此最新版本的报表服务存在不利之处可能会使许多管理员感到沮丧。

不推荐使用的功能#1:消失的排序 (Deprecated Feature #1: The Disappearing Sort)

  1. Security property 担保财产

    In the organisation that I work for, SSRS is usually accessed by users from multiple departments i.e. Finance, Sales, HR, Customer Services, and IT. Consequently, there is usually a long list of domain users that are granted access to SSRS reports. Thus, one of the useful features in SSRS was the ability to conduct an alphabetical sort of users that have been granted access to reports. The simplest way to do this, has always been to just click on the Group or User field. Figure 1 shows an SSRS 2014 instance with a sorted list of my fictitious users who have been granted access to one of my reports.

    在我工作的组织中,SSRS通常可供来自多个部门(即财务,销售,人力资源,客户服务和IT)的用户访问。 因此,通常会有一长串被授予访问SSRS报告访问权限的域用户。 因此,SSRS中有用的功能之一就是能够按字母顺序排列用户类别,这些用户已被授予访问报告的权限。 最简单的方法就是单击“ 组”或“用户”字段。 图1显示了一个SSRS 2014实例,其中列出了我的虚拟用户的排序列表,这些用户已获得访问我的一个报告的权限。

    Figure 1图1

    However, following the upgrade to SSRS 2016, I now have an unsorted list of groups and users (i.e. user WIN-9P7O5S87UBG\Sifiso shown in Figure 2, is now ahead of user WIN-9P7O5S87UBG\abcUser). Instead of users being sorted alphabetically, it seems like SSRS 2016 is now sorting users based on the date they were granted access to the report. Furthermore, the ability to sort users by clicking on the Group or User field, has been removed.

    然而,在升级到SSRS 2016以下,我现在有组和用户的无序列表( 如图2所示即用户WIN-9P7O5S87UBG \ Sifiso,现在是领先的用户WIN-9P7O5S87UBG \ abcUser)。 似乎用户没有按字母顺序排序,而是SSRS 2016现在根据用户被授予访问报告的日期对其进行排序。 此外,已经删除了通过单击“ 组”或“用户”字段对用户进行排序的功能。

    Figure 2图2

  2. As indicated earlier, our SSRS instance contains hundreds of items that are accessed by users from various departments. Thus, part of administering such a report server instance involves doing a quick search to get to some items. Figures 3 and 4 shows the two search result pages against an SSRS 2014 and SSRS 2016, respectively.

    如前所述,我们的SSRS实例包含数百个项目,供各个部门的用户访问。 因此,管理此类报表服务器实例的一部分涉及进行快速搜索以获取某些项目。 图3 4分别显示了针对SSRS 2014和SSRS 2016的两个搜索结果页面。

    Figure 3图3

    Figure 4图4

    What it basically comes down to, is that our favourite search results page has also been disadvantaged by the upgrade as we are no longer unable to:

    基本上可以归结为,我们最喜欢的搜索结果页面也由于升级而处于不利地位,因为我们不再无法:

    • Sort search results 排序搜索结果
    • Bulk-Delete several search results 批量删除多个搜索结果
    • Bulk-Move several search results 批量移动多个搜索结果
    • Change search results view from list to tile, (and vice versa) 将搜索结果视图从列表更改为图块,反之亦然

不建议使用的功能2:上传期间无法重命名项目 (Deprecated Feature #2: Inability to Rename Items During Upload)

Ideally if you have a good naming convention in place for all your SSRS development, then this deprecated feature shouldn’t really be an issue for you but the fact is most SSRS developments do not follow good naming conventions, so that’s why the removal of this feature can be very frustrating for most report server administrators. Basically, versions prior to SSRS 2016 used to give you an ability to rename a file during the upload, particularly when you are uploading a file whose name already exists in the report server.

理想情况下,如果您为所有SSRS开发制定了良好的命名约定,则此折旧功能对您来说并不是真正的问题,但事实是大多数SSRS开发都不遵循良好的命名约定,因此正因为如此,对于大多数报表服务器管理员而言,此功能可能非常令人沮丧。 基本上,SSRS 2016之前的版本使您能够在上载期间重命名文件,尤其是当您上载其名称已存在于报表服务器中的文件时。

For instance, in Figure 5, I am attempting to upload an SSRS Shared Dataset whose name already exists in the report server. As expected, I get a warning message that informs me that the item name is already in use. To get around this, I renamed the Shared Dataset from DataSet1 to Dataset2, proceeded to click OK button and the upload was successful.

例如,在图5中 ,我试图上载其名称已存在于报表服务器中的SSRS共享数据集。 不出所料,我收到一条警告消息,通知我该商品名称已被使用。 为了解决这个问题,我将共享数据集从DataSet1重命名为Dataset2 ,然后单击OK按钮,上传成功。

This ability to rename an item during an upload in SSRS 2016 has unfortunately been discontinued. As shown in Figure 6, you are now only allowed to either overwrite an existing item or cancel the upload operation.

不幸的是,在SSRS 2016中的上传过程中,重命名项目的功能已被终止。 如图6所示,现在只允许您覆盖现有项目或取消上载操作。

不推荐使用的功能#3:消失的树层次结构 (Deprecated Feature #3: The Disappearing Tree Hierarchy)

One of the tasks of a report server administrator typically involves deploying and configuring reports. You often have to configure report data sources and shared datasets as you have to change connection strings to point to production. One benefit of configuring data source and datasets – especially when a report has multiple of these – was that when you click browse to look for a data source or dataset, you would get a tree structure that is easy to navigate.

报表服务器管理员的任务之一通常涉及部署和配置报表。 您通常必须配置报告数据源和共享数据集,因为您必须更改连接字符串以指向生产。 配置数据源和数据集的一个好处-特别是当报表包含多个数据源时-单击浏览以查找数据源或数据集时,您将获得易于浏览的树状结构。

For instance, the report shown in Figure 7 has multiple shared datasets, one of which (DataSet1) has already been configured, when I click on the Browse button to configure DataSet2, the dataset I last selected is set as the default for Dataset2. Now, I can either select the default dataset or navigate to something else. The point is, these default dataset paths usually saves considerable amount of time from having to click the root report manager folder every time you need to get to datasets stored within various sub-folders.

例如, 图7所示的报告具有多个共享数据集,其中一个( DataSet1 )已配置,当我单击Browse按钮配置DataSet2时 ,我最后选择的数据集被设置为Dataset2的默认数据集。 现在,我可以选择默认数据集,也可以导航到其他内容。 关键是,每次需要访问存储在各个子文件夹中的数据集时,这些默认数据集路径通常都可以节省大量时间,而不必单击根报表管理器文件夹。

Well, not only has default dataset paths been removed in SSRS 2016, the tree hierarchy structure that made identifying datasets so easy has also been removed. As it can be seen in Figure 9, when I try to configure DataSet2, I am not redirected to the path of the last dataset that I selected (in this case DataSet1), instead I am redirected to a dataset root folder shown in Figure 10. If the dataset that I am looking for is 3 levels down, then I will have to click on sub-folders until I get to the right folder!

好吧,不仅在SSRS 2016中删除了默认数据集路径,而且还使树状层次结构使识别数据集变得如此容易也已删除。 从图9中可以看到,当我尝试配置DataSet2时 ,我没有重定向到我选择的最后一个数据集的路径(在本例中是DataSet1 ),而是重定向到了图10所示的数据集根文件夹。 。 如果我要查找的数据集下降了3级,则必须单击子文件夹,直到找到正确的文件夹!

不建议使用的功能4:“上下文”菜单中的减少的选项 (Deprecated Feature #4: Reduced options in the Context Menu)

As an SSRS administrator, the context menu is one of the convenient ways to accessing some SSRS item properties. For instance, if you need to add a user to a report, you would open the context menu associated with a given report and then click Security as shown in Figure 11. This would take you directly to the Security property of the report.

作为SSRS管理员,上下文菜单是访问某些SSRS项目属性的便捷方法之一。 例如,如果需要将用户添加到报告中,则可以打开与给定报告关联的上下文菜单,然后单击“ 安全性 ”, 如图11所示。 这将直接将您带到报告的“ 安全性”属性。

Well, if you would attempt to replicate these actions in SSRS 2016 you would notice that the Security option has been removed from a report’s context menu.

好吧,如果您尝试在SSRS 2016中复制这些操作,您会注意到“安全性”选项已从报表的上下文菜单中删除。

Other options that have been removed from a report’s context menu include the ability to Create Linked Report. The Security option has been removed across all SSRS item types including data sources and datasets. Furthermore, the data source item type has also had View Dependent Items option removed from the context menu – as shown in Figures 13 and 14.

从报表的上下文菜单中删除的其他选项包括“ 创建链接的报表”的功能 。 已删除所有SSRS项目类型(包括数据源和数据集)的“安全性”选项。 此外,数据源项目类型还从上下文菜单中删除了“ 查看相关项”选项- 如图1314所示

不建议使用的功能5:禁用的超链接 (Deprecated Feature #5: The Disabled Hyperlink )

Have you ever attempted to run a report and received an error message relating to some invalid dataset or connection string? Well, one of the first things I like to do in that situation is to click on the report’s hyperlink, as shown in Figure 15. Such a hyperlink click (in versions of SSRS prior to SSRS 2016), would redirect you to a manage page in which you could navigate accordingly to fix the invalid report dataset.

您是否曾经尝试运行报告并收到与某些无效的数据集或连接字符串有关的错误消息? 嗯,在这种情况下,我想做的第一件事就是单击报表的超链接, 如图15所示。 这样的超链接单击(在SSRS 2016之前的SSRS版本中)会将您重定向到管理页面,您可以在其中相应地导航以修复无效的报告数据集。

Unfortunately, this ability to click on the report name so to be redirected into the manage page has been removed in SSRS 2016, as shown in Figure 16.

不幸的是,单击报告名称以将其重定向到管理页面的功能已在SSRS 2016中删除, 如图16所示。

Instead of the previously easier and convenient way of getting to the manage report page, you are restricted to doing the following:

只能使用以下方法来代替以前访问管理报告页面的简便方法:

  1. Click on the folder containing a given report 单击包含给定报告的文件夹
  2. Identify the report that you want to fix 确定您要修复的报告
  3. Right click on it to get to the context menu, and finally 右键单击它以进入上下文菜单,最后
  4. Manage! 管理

It’s ridiculous!

太荒谬了!

参考资料 (References)

  • Report Datasets 报告数据集
  • Interactive Sort 互动排序
  • Manage Shared Datasets 管理共享数据集

翻译自: https://www.sqlshack.com/top-5-deprecated-features-in-reporting-services-2016/

Reporting Services 2016中不推荐使用的5大功能相关推荐

  1. 使用游标正确提取SQL Server数据并将其放置在Reporting Services矩阵中

    介绍 ( Introduction ) In our last two chats, we discussed enterprises that have had financial years th ...

  2. sql表格模型获取记录内容_SQL Server和BI –如何使用Reporting Services 2016记录表格模型

    sql表格模型获取记录内容 介绍 (Introduction) A few weeks back I had been working on an interesting proof of conce ...

  3. 单包攻击_SQL Server Integration Services 2016中的单包部署

    单包攻击 SQL Server 2016 has some exciting enhancements to SQL Server Integration Services. In this arti ...

  4. 在Reporting Services (RDL)中自动生成大量列

    目录 包含大量列的RDL文件 背景 设置 使用代码 包含大量列的RDL文件 使用自动化无法创建包含大量列的SSRS报告.至少我能够找到.因此,在本文中,我将分享一些编写的代码,这些代码可以使用现有的S ...

  5. 扩展Reporting Services和SQL Server 2016中的更改

    Scaling out Reporting services to multiple nodes, in itself, is a relatively simple process. It's wh ...

  6. 如何在SQL Server Reporting Services中使用表达式来创建有效的报告

    介绍 (Introduction) As many of you by now know, I am a fan of utilizing expressions within Reporting S ...

  7. SQL Server Reporting Services(简称SSRS)

    主要说说关于SSRS的安装.部署和配置问题. SSRS的安装 Reporting Services作为SQL Server的一个组件,自然是要伴随SQL Server一起安装了.目前SQL Serve ...

  8. Reporting Services 的伸缩性和性能表现规划(转载)

    简介 Microsoft? SQL Server? Reporting Services 是一个将集中管理的报告服务器具有的伸缩性和易管理性与基于 Web 和桌面的报告交付手段集于一身的报告平台.Re ...

  9. Reporting Services 安装的备份和还原操作

    Reporting Services 安装的备份和还原操作 本主题概要介绍了 Reporting Services 安装中使用的所有数据文件,并介绍应在何时以及如何备份这些文件.为报表服务器数据库文件 ...

最新文章

  1. windows下多版本python安装与pip安装和pip使用 吐血总结
  2. 不允许使用抽象类类型的对象怎么办_Java基础——面试官:你来说说抽象类和接口的区别...
  3. 表单验证AngularJs
  4. opencv3——ANN算法的使用
  5. 怎样使用element-starter快速搭建ElementUI项目
  6. ef1a启动子_常见的真核和原核表达系统的启动子(promoters)
  7. Mysql报错时区错误invalid timezone
  8. 积分竞猜网php源码_贵州省网络安全知识竞赛个人赛Writeup
  9. 【NOIP2008】【Vijos1493】传纸条
  10. 两年前,梦开始的地方.
  11. 卡尔曼滤波估matlab算法,INS-matlab 利用卡尔曼滤波算法估计惯导系统状态量的源代码~谢谢分享 - 下载 - 搜珍网...
  12. layui数据表格实现内容筛选的全选和反选功能
  13. Backtrader量化平台教程(六)Analyzer
  14. 【量化入门】通过几种常见的量化策略框架,学习量化炒股
  15. http 请求405 错误
  16. /dev/null 21 详解
  17. 电子通信类相关专业面试
  18. python pandas 分割DataFrame中的字符串及元组
  19. ipv6u前缀地址数中/32,/48,/64含义跟一些相关资料
  20. 计算机主板上的fan,电脑主板上CPU_FAN、SYS_FAN、CHA_FAN、CPU_OPT接口知识科普

热门文章

  1. xwpython aui 子窗口-Python/wxPython:AUI管理器,防止面板离开Fram
  2. 自定义标签处理器类的生命周期
  3. jQuery--基本选择器
  4. HDU 6319(单调队列)
  5. 【iCore4 双核心板_ARM】例程十一:DMA实验——存储器到存储器的传输
  6. Mysql-2-数据库基础
  7. ACM 美素数 (没AC)
  8. 结构模式--之--享元模式
  9. 今后几个月的IT读书计划
  10. 《我的WCF之旅》博文系列汇总