SQL 2000 报告服务安全性

发布于 2024-11-03 04:53:06 字数 96 浏览 0 评论 0原文

由于公司更改了网络配置,我的报告订阅变得不可见。报告仍按计划运行,但订阅不可维护,因为它是不可见的。除了删除并重新创建所有 150 份报告之外,是否可以采取其他措施来修复该问题?

My report subscriptions became invisible as company has chaned network configuration. The reports still run by schedule but subscription is not maintainable as it is invisible. Is it possible to do anything to fix it besides deleting and recreating all 150 reports?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

不可一世的女人 2024-11-10 04:53:06

自从我对 SSRS 2000 做了很多工作以来,已经有几年了。(@John Saunders:它大约在 2003 年发布,而不是与最初的产品一起发布。)

我不确定问题的目标是什么:制作报告再次可见或停止订阅?

如果要使报告再次可见:

  • 您是否尝试过报告管理器 url 和报告服务器 url?
  • 报告服务器 URL 是订阅用来生成报告的地址,因此它可能仍然可用。此 URL 通常以 /reportserver/ 结尾
  • 您收到什么错误,或者日志中是否有任何消息可让您了解问题所在?
  • 能否将 Reporting Services 升级到 SQL 2005 或 SQL 2008?

如果目标是停止孤立订阅:这些是 SQL 代理运行的作业。它们有混乱的 GUID 名称,但这些名称链接回 Reporting Services 表:
来自 SQL Server Central

SELECT
   Schedule.ScheduleID AS SQLAgent_Job_Name,
   Subscriptions.Description AS sub_desc,
   Subscriptions.DeliveryExtension AS sub_delExt,
   [Catalog].Name AS ReportName,
   [Catalog].Path AS ReportPath
FROM       ReportSchedule
INNER JOIN Schedule ON ReportSchedule.ScheduleID = Schedule.ScheduleID
INNER JOIN Subscriptions ON ReportSchedule.SubscriptionID = Subscriptions.SubscriptionID
INNER JOIN [Catalog] ON ReportSchedule.ReportID = [Catalog].ItemID AND Subscriptions.Report_OID = [Catalog].ItemID

It's been a couple of years since I've done much with SSRS 2000. (@John Saunders: It was released in about 2003, not with the initial product.)

I'm not sure what the question's goal is: to make the reports visible again or to stop the subscriptions?

If to make the reports visible again:

  • Have you tried both the report manager url and the reportserver url?
  • The report server url is what the subscriptions use to generate the reports, so it may still be available. This url typically ends with /reportserver/
  • What error do you receive, or are there any messages in the logs that let you see what the problem is?
  • Can you upgrade Reporting Services to SQL 2005 or SQL 2008?

If the goal is to stop the orphaned subscriptions: These are jobs that the SQL Agent runs. They have messy GUID names, but those link back to the Reporting Services tables:
From SQL Server Central

SELECT
   Schedule.ScheduleID AS SQLAgent_Job_Name,
   Subscriptions.Description AS sub_desc,
   Subscriptions.DeliveryExtension AS sub_delExt,
   [Catalog].Name AS ReportName,
   [Catalog].Path AS ReportPath
FROM       ReportSchedule
INNER JOIN Schedule ON ReportSchedule.ScheduleID = Schedule.ScheduleID
INNER JOIN Subscriptions ON ReportSchedule.SubscriptionID = Subscriptions.SubscriptionID
INNER JOIN [Catalog] ON ReportSchedule.ReportID = [Catalog].ItemID AND Subscriptions.Report_OID = [Catalog].ItemID
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文