Reporting Services Implementation

We are just now looking at implementing Reporting Services, and I would like
to pose a few questions.
1. What are the issues (performance, etc)/dangers (security, etc) of
installing Web Services on a SQL Server?
2. What, if anything, can be done to minimize these issues?
3. I would like to get a feeling for how most shops are setting up RS. Are
you putting it with an existing SQL installation, or are installing
separately?
4. Do you have success/horror stories concerning RS?
SteveOne thing you don't mention is whether this is an intranet or internet
scenario. Many DBAs are very hesitant to have anything other than the
database engine running on the server. Not just for performance but for
security. My feeling is that for intranet applications DBAs better adjust
because IIS will be happening on the same server for many scenarios of which
RS is one of them. If you have the CPU bandwidth then RS running on the same
server is no big deal from a performance issue. The main issue is that you
should harden IIS. Plus use integrated security.
If an internet application then I would suggest that the data (versus the
object caching) should be behind the firewall. Note that RS needs SQL Server
for its object caching. You can have SQL Server local on the server just for
that and the data can be somewhere else.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"hoo-t" <hoo-t@.discussions.microsoft.com> wrote in message
news:C1456869-61D8-4646-AE15-318CAAA9D972@.microsoft.com...
> We are just now looking at implementing Reporting Services, and I would
like
> to pose a few questions.
> 1. What are the issues (performance, etc)/dangers (security, etc) of
> installing Web Services on a SQL Server?
> 2. What, if anything, can be done to minimize these issues?
> 3. I would like to get a feeling for how most shops are setting up RS.
Are
> you putting it with an existing SQL installation, or are installing
> separately?
> 4. Do you have success/horror stories concerning RS?
> Steve
>|||Bruce,
Thanks for your response. The implementation that is currently being looked
at would be intranet, as would most if not all our implementations. However,
I wanted to leave that issue open in order to get the broadest viewpoint, as
was presented with your post.
As you said, IIS is being installed for reasons other than Reporting
Services. In fact, most of our SQL Servers do have it installed, but the Web
Services portion is disabled. Reporting Services requires Web Services,
which opens up a whole new can of worms!
Steve
"Bruce L-C [MVP]" wrote:
> One thing you don't mention is whether this is an intranet or internet
> scenario. Many DBAs are very hesitant to have anything other than the
> database engine running on the server. Not just for performance but for
> security. My feeling is that for intranet applications DBAs better adjust
> because IIS will be happening on the same server for many scenarios of which
> RS is one of them. If you have the CPU bandwidth then RS running on the same
> server is no big deal from a performance issue. The main issue is that you
> should harden IIS. Plus use integrated security.
> If an internet application then I would suggest that the data (versus the
> object caching) should be behind the firewall. Note that RS needs SQL Server
> for its object caching. You can have SQL Server local on the server just for
> that and the data can be somewhere else.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "hoo-t" <hoo-t@.discussions.microsoft.com> wrote in message
> news:C1456869-61D8-4646-AE15-318CAAA9D972@.microsoft.com...
> > We are just now looking at implementing Reporting Services, and I would
> like
> > to pose a few questions.
> > 1. What are the issues (performance, etc)/dangers (security, etc) of
> > installing Web Services on a SQL Server?
> > 2. What, if anything, can be done to minimize these issues?
> > 3. I would like to get a feeling for how most shops are setting up RS.
> Are
> > you putting it with an existing SQL installation, or are installing
> > separately?
> > 4. Do you have success/horror stories concerning RS?
> >
> > Steve
> >
>
>