all groups > sql server reporting services > december 2004 >
You're in the

sql server reporting services

group:

Deploying Reports To Remote Locations


Deploying Reports To Remote Locations Smit-Dog
12/13/2004 9:45:01 AM
sql server reporting services:
Hello,

I am a new SQL Reporting Services developer, and have a couple of newbie
questions.

1) I understand that SQL Reporting Services (SRS) is free with every
licensed copy of SQL Server 2000. I downloaded what appears to be an
"evaluation" copy of SRS. How do you install / license SRS on a server that
has a licensed copy of SQL Server 2000? Is there a separate download
media/CD? How do you license / activate SRS properly?

2) I would like to develop a SRS report remotely for a customer, and then
deploy it on their intranet at their location. Basically all development is
off-site, and I will travel onsite to install the completed SRS report. They
do not have a licensed copy of Visual Studio .NET, so none of the
development/maintenance will be done on their server. When I go to install
SRS on their server, I will only install the Server components, not the
client components. With that said, how do go about getting the actual report
installed / deployed on their server? I can do it locally on my development
box using "deploy" from within VS.NET, but how do I do it "manually" on a box
without VS.NET? What report "files" do I need to copy from my machine, and
what needs to be setup in IIS?

Re: Deploying Reports To Remote Locations Smit-Dog
12/13/2004 10:19:08 AM
Thanks for the quick reply Bruce!

I'll see if I can get the "offical" version via MSDN.

I'll check out the scripting example. Hope it's not too involved. I figured
that it would not be as straight forward as copying a few files.

- Bill

[quoted text, click to view]
Re: Deploying Reports To Remote Locations Smit-Dog
12/13/2004 11:41:05 AM
It appears that the Report Manager browser interface allows you to upload an
RDL file from a file system directly into the Report Server database. Very
cool!

But.... I imagine that since the data source info is different between the
two environments (production server versus development laptop) and since the
RDL contains the data source definition, this might not work 100%. Still need
to do some more digging. Perhaps you can change the data source for a report
once it's been uploaded into the production server.

[quoted text, click to view]
Re: Deploying Reports To Remote Locations Bruce L-C [MVP]
12/13/2004 11:59:47 AM
You can order a CD with RS (i.e. a non-evaluation version). MSDN has it as
well.

There are no activation that occurs, just install it. You do have to have
the correct version of SQL Server when installing.

To deploy without you can script the deployment. I believe an example of
this ships with RS.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services


[quoted text, click to view]

Re: Deploying Reports To Remote Locations Bruce L-C [MVP]
12/13/2004 12:43:26 PM
The reason it is not just copying files is that your rdl files do not exist
on the server (search it, you won't find them). The reports are stored in
the database.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services


[quoted text, click to view]

Re: Deploying Reports To Remote Locations Bruce L-C [MVP]
12/13/2004 1:59:06 PM
The best way to do this is to used shared datasource. I never define a
datasource for a particular report. I might have two shared datasources in a
project though. Then you have your shared datasource be defined differently
on your development machine than it is in production. Only the name of the
shared datasource needs to stay the same.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]

AddThis Social Bookmark Button