RayFD


Hello everyone,

Greetings! I just found this group after wasting hours trying to make
SSRS work with databases that are already created (that is, the DBA
created two empty databases for me, X and XTempDB).


I keep getting "this connection string is invalid can't use this to
connect to SQL Server" in the Database Setup tab.


The problem is that to create its own database, SSRS needs dbcreator
and securityadmin roles (please correct me if I'm wrong here). And I'm
having a helluva problem trying to convince the DBA to give me
temporary dbcreator and securityadmin roles!

Is there any document or
something that I can use to convince him that SSRS will not do
anything like recreating the login (because he said that the login has
already existed and has its role set up in many other databases)

Any help, pointers, suggestions, etc. is very much appreciated.


Thanks,
Ray




Re: Does SSRS have to create its own database? Or can it use an existing empty one?

Adam Tappis - IMGroup


The databases are only created upon install.

In the usual scenario a person with the relevant priveladges e.g. your DBA, should actually install SSRS for you.

If he doesn't know how then do it over netmeeting.







Re: Does SSRS have to create its own database? Or can it use an existing empty one?

RayFD

Hi Adam,

Thanks very much for your reply. I passed the DB creation script generated using SSRS Config Tool to the DBA, and now he refuses to run in on the grounds that it grants EXECUTE rights to system stored procedures such as sp_delete_job. I'm thinking that maybe the whole installation and administration of SSRS should just be done by the DBA instead.

Is that typical, e.g.: SSRS managed entirely by DBA, and we developer merely get assigned roles as content publisher, etc. (We're the first one in our organization to do this, and most books and articles that I read don't discuss this--they either assume that you're setting it up in your development database, or you're already a DBA.)

Thanks,

Ray






Re: Does SSRS have to create its own database? Or can it use an existing empty one?

Adam Tappis - IMGroup

You should think of installation, configuration and administration separately rather than assuming the developer does it all.

In terms of reporting services, your company should evaluate reporting services as a product, inspect the changes it makes on the system (security etc...) and determine whether it can operate in your environment rather than the DBA making that decision.

The way I see it, I would split the responsibility as follows:

  • Installation - SA and DBA
  • Configuration - DBA, Web Admin and Developer
  • Server Administration - DBA
  • Security Administration - depends on environment
    • DEV - it would be the developer
    • Production - Support personnel






Re: Does SSRS have to create its own database? Or can it use an existing empty one?

BobP - BIM

The reason it is granting execute rights to those system store procedures such as sp_delete_job is for scheduling subscriptions. Without this, SSRS could not create the SQL Agent job needed to schedule the subscription.

BobP