We help IT Professionals succeed at work.

how to tell which package an ssrs report is deployed from

kelleigh2
kelleigh2 asked
on
Hi -

We had our developer leave and he left a total mess behind. He deployed packages (both ssis and ssrs) from VS 2005, 2008, and 2010 and everything is located in Virtual Source Safe.  His naming convention, unfortunately, was horrible, so it doesn't tell us which version of VS the package is, nor to which servers they've been deployed.  In particular we've been having some trouble matching deployed reports to their packages. Does anyone know of any way to figure out where (which package) a deployed report came from?

Thanks.
Comment
Watch Question

Jason YousefSr. BI  Developer

Commented:
Let me shed some light, the package is an SSIS package, SSRS reports can;t be deployed from a SSIS packages.
He should have Solutions and projects for each project he's working at.

In SSRS if you look at the Source code of the report .RDL, as an XML file, the first line will have the SQL server version.

for SSIS if you open a package under a different version, higher for example, it'll ask you to upgrade, and it's not a backward compatible, you can't reverse the upgrade, so always keep a backup.

He had to keep documentation for every project and his manager should keep these things in place and awayes ask for documentations.

Author

Commented:
I understand there is a difference between the SSIS and SSRS packages - we have issues with both. I can usually figure out what SSIS package belongs to which SQL Job, but the SSRS packages are more difficult.

There are solutions and projects listed all over the place, but they don't tie together. For example,we have a deployed report that in reporting services is listed as \\serverx_reportingservices\fullreports\reportx, but if you go and look at the SSRS packages, there isn't a project or package called "full reports", so we have no idea which SSIS package this actually came from. That's why I was hoping there was something in the SQL database they are deployed to that might give us some clue as to what the original package name was.

He did NOT keep documentation - that is part of the issue. We are flying blind and there is a ton of guesswork going on. Sometimes we can find the actual table or function that the report pulls from by going through the database, but not the actual report to update or change it. In some cases he upgraded the report to a new version, made some changes, but didn't deploy it, so we don't have the original either.
Sr. BI  Developer
Commented:
WOW,that's a total mess, anyway there's no way to figure it other than manually, opening each solution or project and check the contents, trying to figure out the source and destination and re-organize it in your way.

If you need more help, you could upload the stuff for people to look at, but don't include personal info or passwords.

or even hire an expert from EE, by clicking on the HIRE ME button on any expert's profile, to remote in and help with some work load and documentation.

Author

Commented:
That's what I was afraid of. Oh well - doesn't hurt to ask! Thanks!!
Jason YousefSr. BI  Developer

Commented:
let me know if you need further help with SSIS or SSRS documentation, that's my e-mail if you have any special questions  Huslayer @ hotmail.com.

Thanks
Jason Yousef

Author

Commented:
Perfect! We might take you up on that since we haven't found a good way to do it yet. Thanks so much!
Jason YousefSr. BI  Developer

Commented:
Great I love challenges :)