Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSRS Reports deployment to Production Server


SSRS Reports deployment to Production Server

Author
Message
Mohan Kumar VS
Mohan Kumar VS
Old Hand
Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)

Group: General Forum Members
Points: 304 Visits: 344
Hi

I had created few SSRS reports on the development environment. Now I need to deploy those reports to the production environment. The production environment server name & database names are different from development environment.

Kindly let me know the proper procedure for deployment.


Rgds
Mohan Kumar VS
Stewart "Arturius" Campbell
Stewart "Arturius" Campbell
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6371 Visits: 7192
It depends on
> deployment procedures in your workplace,
> accepted levels of authority,
> source code management,
etc

off the cuff, there are two ways of deploying a report into production
> in the solution, properties, change the TargetServerURL to the production server's URL
> in SSRS production, select "Upload File", which will take you to a screen where you browse to the report to be deployed.

____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
Mohan Kumar VS
Mohan Kumar VS
Old Hand
Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)

Group: General Forum Members
Points: 304 Visits: 344
Thanks a lot.

Earlier we were using Crystal Reports. Now we are planning to move to SSRS.

Reg.:
It depends on
> deployment procedures in your workplace, --
> accepted levels of authority,
> source code management,

We just want those reports to work fine. Source Code management is done using VSS.

You have mentioned:
> in the solution, properties, change the TargetServerURL to the production server's URL
> in SSRS production, select "Upload File", which will take you to a screen where you browse to the report to be deployed.

Will it work fine even if the server names are different?

Thanks again. I will try & let you know.

Rgds
Mohan Kumar
Stewart "Arturius" Campbell
Stewart "Arturius" Campbell
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6371 Visits: 7192
Mohan Kumar VS (7/21/2010)
Will it work fine even if the server names are different?


One recomendation is to have generic shared data sources for all environments (i.e. the datasource names will be the same accross DEV, UAT & PRD, just the connection strings will differ).
Therefore, when the reports are deployed, they will automatically connect to the relevant databse(s).

____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
Mohan Kumar VS
Mohan Kumar VS
Old Hand
Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)

Group: General Forum Members
Points: 304 Visits: 344
Thanks again for your prompt response.

Rgds
Mohan Kumar
Mohan Kumar VS
Mohan Kumar VS
Old Hand
Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)Old Hand (304 reputation)

Group: General Forum Members
Points: 304 Visits: 344
Hi...

We were provided with VPN connection to access the production server and are able to view the reports deployed in the production server through the report server link.

Today, we created one test report and provided the Production Server link in the target url and deployed. It asked for the credentials for that system. And the deployment was successful and we are able to view the report.

My question is that, we never mentioned the Production server database name, then how it was able to retrieve the report? For clarifying this I stopped the Sql Services in the development environment. Then also the report was working fine. The database names are different in DEV & Production environments.

Kindly clarify.

Rgds
Mohan Kumar VS
Stewart "Arturius" Campbell
Stewart "Arturius" Campbell
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6371 Visits: 7192
> did you use a shared data source name when the test report was built?
> If so, does this shared data source exist in the production environment?
> If the data source did already exist (you can check this in the Report Services Reports/Pages/Folder.aspx page), which database is it pointing to?

reason for my questions is that, when reports are deployed using an existing shared data source, the data source is not replaced, but the existing one will automatically be used by the report.
to check this, in the reports properties, go to the data sources tab and see which datasource it is linked to.

____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
Greg Edwards-268690
Greg Edwards-268690
SSC Eights!
SSC Eights! (929 reputation)SSC Eights! (929 reputation)SSC Eights! (929 reputation)SSC Eights! (929 reputation)SSC Eights! (929 reputation)SSC Eights! (929 reputation)SSC Eights! (929 reputation)SSC Eights! (929 reputation)

Group: General Forum Members
Points: 929 Visits: 8322
If RS is on the database server, and . or localhost is used in the data source, this could be another possible reason.
Take the time to make sure you understand what is happening when you deploy, it will save you trouble down the road.
Greg E
raijin355
raijin355
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
Points: 10 Visits: 4
Morning all,
It is my first post here and mainly my issue is very similar to this thread hence I wanted to keep amount of threads created to minimal that said;
Environment: Sql server 2012 with SSRS in Sharepoint integrated mode 2013.
Problem: Have created and successfully deployed reports to both Dev and Prod Sharepoint environments. But like the original poster have the same issue; how do I change depending on the environment the data set accessed by the report?
If possible a bullet point list that these are the set of things I need to change be great. I like to keep macro things as simple as possible as in our profession we deal with enough complications.
Additional info:
1) I have in the properties of SSRS in Visual Studios 2012 been able to set correct deployment paths to both sharepoint dev and prod. So 1 click deployment to both environments work. and tested it works. Using "shared dataset" that points to dev for now.
2) Many of the prod databases are not even created yet as we are relatively new environment and I would like input if possible of best practice to use here i.e. industry standards on if dev and prod db names should remain same; etc. In this project I do have control over prod and can dictate how our BI team wants the DB/tables named etc. In the past IT teams with DBAs have done this for me.
Thanks much in advance for input and any other questions I can answer from my side plz fire away.
-Darkraijin.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search