Remote Reporting Server

Can you have SQL 2005 reporting services installed on a front end web server
without a local SQL engine (i.e. the reports DB is on a remote engine).
Reporting is running and working on the remote back end server which has the
engine as well.
If this is so, can the back end server be SQL 2005 Enterprise SQL 64 bit,
and the front end web server be SQL 2005 Enterprise SQL 32 bitOn Feb 11, 2:06 pm, "John Hiebert" <johndhieb...@.hotmail.com> wrote:
> Can you have SQL 2005 reporting services installed on a front end web server
> without a local SQL engine (i.e. the reports DB is on a remote engine).
> Reporting is running and working on the remote back end server which has the
> engine as well.
> If this is so, can the back end server be SQL 2005 Enterprise SQL 64 bit,
> and the front end web server be SQL 2005 Enterprise SQL 32 bit
As long as your Report Manager and virtual directories for SSRS are on
the front-end server and the back-end server includes the ReportServer
and ReportServerTempDB databases, you should be fine with varying
editions of SQL Server. Of course, your SQL Server license for SSRS is
required in the location of your ReportServer and ReportServerTempDB
databases. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||We have a similar situation but we want SSRS to run on an internal web
server. So teh user has access only to the fron-end web server, and upon a
report request, he'll be forwarded to the internal server for report
processing. The question is how to configure the front-end IIS to run the
reports on the back end IIS.
Thanks,
Gilgamesh
"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:0946c772-2790-4993-ba61-b6cad04b4a79@.y5g2000hsf.googlegroups.com...
> On Feb 11, 2:06 pm, "John Hiebert" <johndhieb...@.hotmail.com> wrote:
>> Can you have SQL 2005 reporting services installed on a front end web
>> server
>> without a local SQL engine (i.e. the reports DB is on a remote engine).
>> Reporting is running and working on the remote back end server which has
>> the
>> engine as well.
>> If this is so, can the back end server be SQL 2005 Enterprise SQL 64 bit,
>> and the front end web server be SQL 2005 Enterprise SQL 32 bit
>
> As long as your Report Manager and virtual directories for SSRS are on
> the front-end server and the back-end server includes the ReportServer
> and ReportServerTempDB databases, you should be fine with varying
> editions of SQL Server. Of course, your SQL Server license for SSRS is
> required in the location of your ReportServer and ReportServerTempDB
> databases. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant|||On Feb 13, 6:56 pm, "Gilgamesh" <Gilgamesh4E...@.aol.com> wrote:
> We have a similar situation but we want SSRS to run on an internal web
> server. So teh user has access only to the fron-end web server, and upon a
> report request, he'll be forwarded to the internal server for report
> processing. The question is how to configure the front-end IIS to run the
> reports on the back end IIS.
> Thanks,
> Gilgamesh
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:0946c772-2790-4993-ba61-b6cad04b4a79@.y5g2000hsf.googlegroups.com...
> > On Feb 11, 2:06 pm, "John Hiebert" <johndhieb...@.hotmail.com> wrote:
> >> Can you have SQL 2005 reporting services installed on a front end web
> >> server
> >> without a local SQL engine (i.e. the reports DB is on a remote engine).
> >> Reporting is running and working on the remote back end server which has
> >> the
> >> engine as well.
> >> If this is so, can the back end server be SQL 2005 Enterprise SQL 64 bit,
> >> and the front end web server be SQL 2005 Enterprise SQL 32 bit
> > As long as your Report Manager and virtual directories for SSRS are on
> > the front-end server and the back-end server includes the ReportServer
> > and ReportServerTempDB databases, you should be fine with varying
> > editions of SQL Server. Of course, your SQL Server license for SSRS is
> > required in the location of your ReportServer and ReportServerTempDB
> > databases. Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
The best way to accomplish this architecture is to utilize Render() as
part of the SSRS Web Service. So, have the front-end application be an
ASP.NET application that references the SSRS web service and the
reports from the back-end SSRS installation.
http://msdn2.microsoft.com/en-us/library/microsoft.wssux.reportingserviceswebservice.rsexecutionservice2005.reportexecutionservice.render.aspx
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant