Monday, March 12, 2012

Reports for Multiple SQL Databases

I would like to setup a Report server... so it can be used as the primary
reporting server for the SQL databases in our environment.
I've installed Windows 2003 Standard Edition, all necessary IIS components,
SQL 2000 (with SP3), Reporting Services (with SP1).
I used a domain account instead of the local service account (perhaps this
was a mistake?).
I can run reports from the AdventureWorks database without incident (since
it is on the same server).
When I try to run a report that references a database on another server... I
either get permission errors or Null SQL user errors.
I suppose this is the standard double-hop authentication issue...
Is there any documentation somebody can point me to that discussing setting
up a reporting server in an environment like this?It seems to me that you are seeing an issue with credentials for the data
source. IYour reports can either have the data source embedded in the report
or the report can reference a shared data source. I recommend using shared
record sources. Look at the credentials of the recordsource. I would not use
integrated but instead use the credentials stored securely in the report
server. I prefer to use a read only account. The advange of this is two
fold. One, you can make sure that only readonly access is allowed via your
reports and two that connection pooling can be fully taken advantage of.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rob Edwards" <RobEdwards@.Landam.com> wrote in message
news:O5GVWqE7EHA.2540@.TK2MSFTNGP09.phx.gbl...
> I would like to setup a Report server... so it can be used as the primary
> reporting server for the SQL databases in our environment.
> I've installed Windows 2003 Standard Edition, all necessary IIS
components,
> SQL 2000 (with SP3), Reporting Services (with SP1).
> I used a domain account instead of the local service account (perhaps this
> was a mistake?).
> I can run reports from the AdventureWorks database without incident (since
> it is on the same server).
> When I try to run a report that references a database on another server...
I
> either get permission errors or Null SQL user errors.
> I suppose this is the standard double-hop authentication issue...
> Is there any documentation somebody can point me to that discussing
setting
> up a reporting server in an environment like this?
>

No comments:

Post a Comment