Comments on: When someone deletes a shared data source in SSRS

By: rsInvalidDataSourceReference Error after Moving RDL Files to Another SSRS Server - DBA Fire

Fri, 08 Dec 2017 07:43:44 +0000

[…] When someone deletes a shared data source in SSRS SSRS: How to fix […]

By: Colin Baldwin

Colin Baldwin — Thu, 07 Jul 2016 17:39:09 +0000

Lifesaver – thank you! 410 reports in my case 🙂

By: Curious

Curious — Wed, 06 May 2015 01:35:41 +0000

If you know of the person that deleted the datasource have them check their recycle bin and then restore it. It’s worked for me in the past without having to update the datasource in each report.

By: Frank

Frank — Fri, 18 Oct 2013 17:51:02 +0000

Great post! I had a slightly different issue: A new report was deployed to 70 servers but most of them didn’t link the data source even though the name was the same. Slight modification to your code plus a little SQL Multi-Script and all is right and good in the world. Thanks!

By: Rob Farley

Rob Farley — Wed, 24 Oct 2012 07:43:33 +0000

Ken,
Yes. If you can redeploy everything and have it sort out which reports use which shared data sources, then that’s even better.
Rob

By: ken

ken — Wed, 24 Oct 2012 07:21:02 +0000

Source control!

By: Rob Farley

Rob Farley — Tue, 23 Oct 2012 22:36:04 +0000

Thanks Valentino.
Regarding the potential many-to-many table required, I agree but can also point out that the parameters are populated using a single ntext column. It breaks first normal form, but there’s definitely a precedent right there. I prefer the way they have it though, and actually wish parameters had their own table too.

By: Valentino Vranken

Valentino Vranken — Tue, 23 Oct 2012 16:15:12 +0000

Hi Rob,
Interesting article! Some feedback:
"There is nothing in dbo.Catalog that describes the actual data sources that the report uses. The default data sources would be part of the Content field, as they are defined in the RDL, but when you deploy reports, you typically choose to NOT replace the data sources. Anyway, they’re not in this table. Maybe it was already considered a bit wide to throw in another ntext field, I’m not sure. They’re in dbo.DataSource instead."
I think it’s logical that the report record does not show what shared data source it uses. As a report can use more than one shared data source and a shared data source can be used by more than one report, an additional table is needed to store the many-to-many relation. But I’m sure you know that? (might I have misunderstood what you meant?)
"Type tells you what kind of item it is. Some examples are 1 for a folder and 2 a report. 4 is linked reports, 5 is a data source, 6 is a report model. I forget the others for now (but feel free to put a comment giving the full list if you know it)."
3 = resource, 8 = dataset, 9 = report part (ref. http://bidn.com/blogs/ChrisAlbrektson/bidn-blog/1083/cross-reference-for-reportserver-dbo-catalog-type)
cya,
@ValentinoV42

By: KP

KP — Thu, 18 Oct 2012 22:13:51 +0000

Great article that I found 1 day too late 🙂 I had this situation last night, luckily it was only 20 reports and not 400. I’ve book marked this article for future reference.

By: Navodita

Navodita — Tue, 16 Oct 2012 16:11:27 +0000

Very informative.. Thanks for the details..