SSRS Reports deployment to Production Server

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 - General » SSRS Reports deployment to Production Server

SSRS Reports deployment to Production Server

Rate Topic

Display Mode

Topic Options

Author

Message

Mohan Kumar VS

Posted Wednesday, July 21, 2010 4:02 AM

SSC Veteran

Group: General Forum Members
Last Login: Tuesday, December 04, 2012 10:13 PM
Points: 283, Visits: 311

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

Stewart "Arturius" Campbell

Posted Wednesday, July 21, 2010 7:01 AM

Hall of Fame

Group: General Forum Members
Last Login: 2 days ago @ 3:48 AM
Points: 3,125, Visits: 4,311

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

Mohan Kumar VS

Posted Wednesday, July 21, 2010 11:47 PM

SSC Veteran

Group: General Forum Members
Last Login: Tuesday, December 04, 2012 10:13 PM
Points: 283, Visits: 311

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

Stewart "Arturius" Campbell

Posted Wednesday, July 21, 2010 11:54 PM

Hall of Fame

Group: General Forum Members
Last Login: 2 days ago @ 3:48 AM
Points: 3,125, Visits: 4,311

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

Mohan Kumar VS

Posted Thursday, July 22, 2010 12:04 AM

SSC Veteran

Group: General Forum Members
Last Login: Tuesday, December 04, 2012 10:13 PM
Points: 283, Visits: 311

Thanks again for your prompt response.

Rgds
Mohan Kumar

Post #956942

Mohan Kumar VS

Posted Thursday, July 22, 2010 7:23 AM

SSC Veteran

Group: General Forum Members
Last Login: Tuesday, December 04, 2012 10:13 PM
Points: 283, Visits: 311

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

Stewart "Arturius" Campbell

Posted Thursday, July 22, 2010 8:18 AM

Hall of Fame

Group: General Forum Members
Last Login: 2 days ago @ 3:48 AM
Points: 3,125, Visits: 4,311

> 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

Greg Edwards-268690

Posted Friday, July 23, 2010 7:15 AM

Right there with Babe

Group: General Forum Members
Last Login: Yesterday @ 7:17 PM
Points: 787, Visits: 5,188

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

« Prev Topic | Next Topic »

Permissions