Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSRS Reports deployment to Production Server Expand / Collapse
Author
Message
Posted Wednesday, July 21, 2010 4:02 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, August 1, 2013 2:51 AM
Points: 283, Visits: 312
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
Post #956210
Posted Wednesday, July 21, 2010 7:01 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 1:05 PM
Points: 3,984, Visits: 5,237
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”
Post #956319
Posted Wednesday, July 21, 2010 11:47 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, August 1, 2013 2:51 AM
Points: 283, Visits: 312
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
Post #956936
Posted Wednesday, July 21, 2010 11:54 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 1:05 PM
Points: 3,984, Visits: 5,237
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”
Post #956940
Posted Thursday, July 22, 2010 12:04 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, August 1, 2013 2:51 AM
Points: 283, Visits: 312
Thanks again for your prompt response.

Rgds
Mohan Kumar
Post #956942
Posted Thursday, July 22, 2010 7:23 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, August 1, 2013 2:51 AM
Points: 283, Visits: 312
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
Post #957169
Posted Thursday, July 22, 2010 8:18 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 1:05 PM
Points: 3,984, Visits: 5,237
> 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”
Post #957215
Posted Friday, July 23, 2010 7:15 AM


Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Friday, September 26, 2014 1:39 PM
Points: 670, Visits: 6,720
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
Post #957939
Posted Monday, February 17, 2014 7:45 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, February 18, 2014 6:58 AM
Points: 2, 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.
Post #1542135
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse