Report databases on existing db server

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

hals_left - 13 Jul 2008 12:42 GMT

I would like to deploy reporting services to 60 users. We have SQL
2005 Standard Edition
I have 1 ad server, 1 IIS server & 1 db server on the dmz.

All the apps on the IIS server have the databases on the db server. I
was hoping to run the reporting services front end webpages on the IIS
server and store the report databases & report data on the db server.
So that we dont have to install SQL server on the IIS server or allow
direct access to the db server

It seems microsoft see this as scale-out architrecture and requires
enterprise edition. This seems odd that we need two copies of sql
server just to do things securely. Can anyone claify if this is the
case or if I have misunderstood.
Thanks.

Reply to this Message

Norman Yuan - 13 Jul 2008 16:44 GMT

Yes, having Reporting Services (an ASP.NET application, by itself) running
on a physical server (IIS server) and have its meta database and data source
on the other physical server (SQL Server) is an ideal configuration. The
catch is, an expensive one if the business operation is fairly small sized,
you need to have SQL Server license for both physical servers (assume it is
processor license).

For a fairly small network (60 users), the SQL Server Reporting Services'
license equipment makes deploying Reporting Services into two physical
server (IIS and SQL Server) almost prohibitive.

>I would like to deploy reporting services to 60 users. We have SQL
> 2005 Standard Edition
[quoted text clipped - 11 lines]
> case or if I have misunderstood.
> Thanks.

Reply to this Message

Bruce L-C [MVP] - 14 Jul 2008 14:37 GMT

Consider the licensing to be like you have purchased MS Office. MS Office
comes with Excel, Word, Powerpoint. Buying a license for MS Office does not
give you the right to install Excel on one PC, Word on another and
Powerpoint on a third. Same is true with SQL Server. SQL Server comes with
SSIS, Analysis Service, Reporting Services and what we mostly think of as
SQL Server the database. Reporting Services is not the only part of SQL
Server that people like to put on their own server. Any place you put RS you
need a SQL Server license. However, what you described is NOT scale out.
Scale out is having multiple RS installed where they all use the same
databases for metadata/object caching.

So, yes you have to purchase SQL Server license for the server running RS.
No, you do not need enterprise. Standard is fine.

Note that having SQL Server DB on the RS server has nothing to do with where
the data resides you are reporting off of.

Signature

Bruce Loehle-Conger
MVP SQL Server Reporting Services

>I would like to deploy reporting services to 60 users. We have SQL
> 2005 Standard Edition
[quoted text clipped - 11 lines]
> case or if I have misunderstood.
> Thanks.

Reply to this Message

hals_left - 15 Jul 2008 08:38 GMT

On 14 Jul, 14:37, "Bruce L-C [MVP]" <bruce_lcNOS...@hotmail.com>
wrote:

> Consider the licensing to be like you have purchased MS Office. MS Office
> comes with Excel, Word, Powerpoint. Buying a license for MS Office does not
[quoted text clipped - 34 lines]
>
> - Show quoted text -

Thanks to both of you for the replies.
I undersand its not actually a scale-out model its just that was the
error I was getting.

Im getting a bit further on this, have installed ReportinServices
component on the app server and got round a version error by re-
installing sp2.

Now when I try to configure reporting services on the "datbase setup"
tab , I get a warning on the line "setting connection info for the
reporting server" saying:

You specified a connection to a report server database that contains
encrption keys
for another report server. If you configuring a scale-out deployment
(Which we agree Im not!) that feature is not supported by this edition
of Report Services. If you want to use this repoer svr db , with the
current rprt svr instance remove the existing encryption keys first

Does this mean the db server is lareday running report services and
its just a case of uninstalling that feature.

Thanks-you

Reply to this Message

Bruce L-C [MVP] - 15 Jul 2008 14:36 GMT

Did reporting services get installed on SQL Server box? What seems to me to
be happening is that RS was installed and it installed the two databases it
needed on the SQL Server database on Machine 1. Either this was done from
some other box somewhere (perhaps a failed installation on the box you are
working on or on Machine 1 itself or from somewhere else). Then you come
along with your new RS install and it sees that someone has already
installed the RS databases (i.e. they already exist on the database server).
So it gives you this message because you are trying to do what looks like a
second RS sharing the databases (i.e. scale out). If you are sure no-one has
already installed RS somewhere and the databases are just left over then go
to the SQL Server and remove the two databases (ReportServer and
ReportServerTempDB). Then re-run your installation of RS.

Signature

Bruce Loehle-Conger
MVP SQL Server Reporting Services

> On 14 Jul, 14:37, "Bruce L-C [MVP]" <bruce_lcNOS...@hotmail.com>
> wrote:
[quoted text clipped - 65 lines]
>
> Thanks-you

Reply to this Message