Administering via SQL Mgmt Studio

Are BUILTIN\Administrators (local admins on the server) the only persons
allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
Services (SSRS)? Can others who may have the Content Manager Role on a
folder or that have the System Administrator Role use SSMS? So far my
experience is only BUILTIN\Admins can use SSMS. Anyting special that must be
done to open up the SSMS to Reporting Services for non BUILTIN\Admins?Why do you want someone, who is not DB admin, to use SSMS to "manage"
reporting services' meta database? Even a db manager has few need to manage
reporting services' database directly. Reporting Services is a web
application and it is managed through a web interfaccce (report manager -
http://serverName/reports).
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> Are BUILTIN\Administrators (local admins on the server) the only persons
> allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
> Services (SSRS)? Can others who may have the Content Manager Role on a
> folder or that have the System Administrator Role use SSMS? So far my
> experience is only BUILTIN\Admins can use SSMS. Anyting special that must
> be
> done to open up the SSMS to Reporting Services for non BUILTIN\Admins?|||I have taken 2 Microsoft Reporting Services (webcast) courses, which have
shown all the administration of SSRS taking place in SQL Server Management
Studio. I use SSMS to conduct other database and A.S. work and consider it
convenient to use SSMS to work SSRS issues, as well. At our location, DBAs
are not allowed to be local admins (except for temporary circumstances) as a
Sarbanes-Oxley design result. I think it is interesting that no one answers
my question, but are very willing to question the circumstances.
"Norman Yuan" wrote:
> Why do you want someone, who is not DB admin, to use SSMS to "manage"
> reporting services' meta database? Even a db manager has few need to manage
> reporting services' database directly. Reporting Services is a web
> application and it is managed through a web interfaccce (report manager -
> http://serverName/reports).
>
> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> > Are BUILTIN\Administrators (local admins on the server) the only persons
> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
> > Services (SSRS)? Can others who may have the Content Manager Role on a
> > folder or that have the System Administrator Role use SSMS? So far my
> > experience is only BUILTIN\Admins can use SSMS. Anyting special that must
> > be
> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
>
>|||>>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
>> shown all the administration of SSRS taking place in SQL Server
>> Management
>> Studio. [..]
>>I think it is interesting that no one answers my question, but are very
>>willing to question the circumstances.
It *is* interesting, but it's also interesting that this is how the courses
recommended that you work, IMHO, since it may not be a viable strategy,
long-term.
Please read below, from Brian Welcker's Weblog
(http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
feedback.
Which parts of administering RS were you particularly interested in doing
via SSMS versus Report Manager (just curious)?
(snip) ---
Watusi (SSRS Management Tools Changes for Katmai)
For Katmai we are considering the removal of namespace management (folders,
reports, data sources, models) from the Reporting Services Add-in for SQL
Server Management Studio (SSMS). In other words, we are considering removing
the 'Home' folder under the Reporting Server node in SSMS.
Why the change?
Customer feedback and usage data indicates that Report Manager and/or
SharePoint are the tools of choice for managing the Report Server namespace,
rather than the SSMS add-in. The design constraints of SSMS mean that any
new namespace functionality is significantly expensive to implement,
specifically adding support for the namespace in SharePoint integrated mode.
For Katmai we want to invest in SharePoint and Report Manager for namespace
management and focus on SSMS as a server-level management tool.
This means that the namespace management functions that are not available in
Report Manager (Model ClickThrough and Model Item Security) will be added to
Report Manager (they are already in SharePoint). Job Management, configuring
System properties, and administering Roles will be moved to SSMS. In
addition, SSMS will be updated to work in SharePoint mode.
If you have feedback about these changes, please feel free to comment.
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> shown all the administration of SSRS taking place in SQL Server Management
> Studio. I use SSMS to conduct other database and A.S. work and consider
> it
> convenient to use SSMS to work SSRS issues, as well. At our location,
> DBAs
> are not allowed to be local admins (except for temporary circumstances) as
> a
> Sarbanes-Oxley design result. I think it is interesting that no one
> answers
> my question, but are very willing to question the circumstances.
> "Norman Yuan" wrote:
>> Why do you want someone, who is not DB admin, to use SSMS to "manage"
>> reporting services' meta database? Even a db manager has few need to
>> manage
>> reporting services' database directly. Reporting Services is a web
>> application and it is managed through a web interfaccce (report manager -
>> http://serverName/reports).
>>
>> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
>> > Are BUILTIN\Administrators (local admins on the server) the only
>> > persons
>> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
>> > Reporting
>> > Services (SSRS)? Can others who may have the Content Manager Role on a
>> > folder or that have the System Administrator Role use SSMS? So far my
>> > experience is only BUILTIN\Admins can use SSMS. Anyting special that
>> > must
>> > be
>> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
>>|||Appreciate your feedback and the insight into Katmai. Looks like it is best
to focus on the Report Manager tool. I am responsible for creating new
folders and assigning new accounts / roles. Most other work is done by the
report developers / folder content managers. I am a previous DBA whose work
has been outsourced. I, currently, provide a role of 'moving' the corp. into
new (DBMS, etc. ) software, then working out the details of handing the
support over to the service provider. I am not yet to the point of moving
the support of SSRS to the service providers, due to budgets, and other
administrative hurdles, so I am the current administrator, beyond the
installation of the product.
"Lisa Slater Nicholls" wrote:
> >>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> >> shown all the administration of SSRS taking place in SQL Server
> >> Management
> >> Studio. [..]
> >>I think it is interesting that no one answers my question, but are very
> >>willing to question the circumstances.
> It *is* interesting, but it's also interesting that this is how the courses
> recommended that you work, IMHO, since it may not be a viable strategy,
> long-term.
> Please read below, from Brian Welcker's Weblog
> (http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
> feedback.
> Which parts of administering RS were you particularly interested in doing
> via SSMS versus Report Manager (just curious)?
> (snip) ---
> Watusi (SSRS Management Tools Changes for Katmai)
> For Katmai we are considering the removal of namespace management (folders,
> reports, data sources, models) from the Reporting Services Add-in for SQL
> Server Management Studio (SSMS). In other words, we are considering removing
> the 'Home' folder under the Reporting Server node in SSMS.
> Why the change?
> Customer feedback and usage data indicates that Report Manager and/or
> SharePoint are the tools of choice for managing the Report Server namespace,
> rather than the SSMS add-in. The design constraints of SSMS mean that any
> new namespace functionality is significantly expensive to implement,
> specifically adding support for the namespace in SharePoint integrated mode.
> For Katmai we want to invest in SharePoint and Report Manager for namespace
> management and focus on SSMS as a server-level management tool.
> This means that the namespace management functions that are not available in
> Report Manager (Model ClickThrough and Model Item Security) will be added to
> Report Manager (they are already in SharePoint). Job Management, configuring
> System properties, and administering Roles will be moved to SSMS. In
> addition, SSMS will be updated to work in SharePoint mode.
> If you have feedback about these changes, please feel free to comment.
> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
> >I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> > shown all the administration of SSRS taking place in SQL Server Management
> > Studio. I use SSMS to conduct other database and A.S. work and consider
> > it
> > convenient to use SSMS to work SSRS issues, as well. At our location,
> > DBAs
> > are not allowed to be local admins (except for temporary circumstances) as
> > a
> > Sarbanes-Oxley design result. I think it is interesting that no one
> > answers
> > my question, but are very willing to question the circumstances.
> >
> > "Norman Yuan" wrote:
> >
> >> Why do you want someone, who is not DB admin, to use SSMS to "manage"
> >> reporting services' meta database? Even a db manager has few need to
> >> manage
> >> reporting services' database directly. Reporting Services is a web
> >> application and it is managed through a web interfaccce (report manager -
> >> http://serverName/reports).
> >>
> >>
> >> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> >> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> >> > Are BUILTIN\Administrators (local admins on the server) the only
> >> > persons
> >> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
> >> > Reporting
> >> > Services (SSRS)? Can others who may have the Content Manager Role on a
> >> > folder or that have the System Administrator Role use SSMS? So far my
> >> > experience is only BUILTIN\Admins can use SSMS. Anyting special that
> >> > must
> >> > be
> >> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
> >>
> >>
> >>
>|||>>Looks like it is best to focus on the Report Manager tool.
I didn't actually mean to say that! I meant to say: if you have cogent
reasons why the work you need to do is better done in Management Studio
rather than Report Manager... then MS deserves to hear your reasons <s>.
OTOH... reading that post closely, it seemed clear to me that the RS team
found the required heirarchical arrangement of functionality in Studio
limiting and not really suited to their purposes. They were probably tired
of shoe-horning features into it. In the Report Manager, they have a much
free-er hand and it was probably not necessary for them to split their
effort between implementation of upcoming features in both UIs.
Going forward, I guess we should be happy if they can focus their energy on
one management UI and we get more new features as a result <s>.
Cheers,
>L<
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:D6726064-25F3-45C6-A9DB-C54CD3778868@.microsoft.com...
> Appreciate your feedback and the insight into Katmai. Looks like it is
> best
> to focus on the Report Manager tool. I am responsible for creating new
> folders and assigning new accounts / roles. Most other work is done by
> the
> report developers / folder content managers. I am a previous DBA whose
> work
> has been outsourced. I, currently, provide a role of 'moving' the corp.
> into
> new (DBMS, etc. ) software, then working out the details of handing the
> support over to the service provider. I am not yet to the point of moving
> the support of SSRS to the service providers, due to budgets, and other
> administrative hurdles, so I am the current administrator, beyond the
> installation of the product.
> "Lisa Slater Nicholls" wrote:
>> >>I have taken 2 Microsoft Reporting Services (webcast) courses, which
>> >>have
>> >> shown all the administration of SSRS taking place in SQL Server
>> >> Management
>> >> Studio. [..]
>> >>I think it is interesting that no one answers my question, but are
>> >>very
>> >>willing to question the circumstances.
>> It *is* interesting, but it's also interesting that this is how the
>> courses
>> recommended that you work, IMHO, since it may not be a viable strategy,
>> long-term.
>> Please read below, from Brian Welcker's Weblog
>> (http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
>> feedback.
>> Which parts of administering RS were you particularly interested in doing
>> via SSMS versus Report Manager (just curious)?
>> (snip) ---
>> Watusi (SSRS Management Tools Changes for Katmai)
>> For Katmai we are considering the removal of namespace management
>> (folders,
>> reports, data sources, models) from the Reporting Services Add-in for SQL
>> Server Management Studio (SSMS). In other words, we are considering
>> removing
>> the 'Home' folder under the Reporting Server node in SSMS.
>> Why the change?
>> Customer feedback and usage data indicates that Report Manager and/or
>> SharePoint are the tools of choice for managing the Report Server
>> namespace,
>> rather than the SSMS add-in. The design constraints of SSMS mean that any
>> new namespace functionality is significantly expensive to implement,
>> specifically adding support for the namespace in SharePoint integrated
>> mode.
>> For Katmai we want to invest in SharePoint and Report Manager for
>> namespace
>> management and focus on SSMS as a server-level management tool.
>> This means that the namespace management functions that are not available
>> in
>> Report Manager (Model ClickThrough and Model Item Security) will be added
>> to
>> Report Manager (they are already in SharePoint). Job Management,
>> configuring
>> System properties, and administering Roles will be moved to SSMS. In
>> addition, SSMS will be updated to work in SharePoint mode.
>> If you have feedback about these changes, please feel free to comment.
>> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
>> >I have taken 2 Microsoft Reporting Services (webcast) courses, which
>> >have
>> > shown all the administration of SSRS taking place in SQL Server
>> > Management
>> > Studio. I use SSMS to conduct other database and A.S. work and
>> > consider
>> > it
>> > convenient to use SSMS to work SSRS issues, as well. At our location,
>> > DBAs
>> > are not allowed to be local admins (except for temporary circumstances)
>> > as
>> > a
>> > Sarbanes-Oxley design result. I think it is interesting that no one
>> > answers
>> > my question, but are very willing to question the circumstances.
>> >
>> > "Norman Yuan" wrote:
>> >
>> >> Why do you want someone, who is not DB admin, to use SSMS to "manage"
>> >> reporting services' meta database? Even a db manager has few need to
>> >> manage
>> >> reporting services' database directly. Reporting Services is a web
>> >> application and it is managed through a web interfaccce (report
>> >> manager -
>> >> http://serverName/reports).
>> >>
>> >>
>> >> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> >> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
>> >> > Are BUILTIN\Administrators (local admins on the server) the only
>> >> > persons
>> >> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
>> >> > Reporting
>> >> > Services (SSRS)? Can others who may have the Content Manager Role
>> >> > on a
>> >> > folder or that have the System Administrator Role use SSMS? So far
>> >> > my
>> >> > experience is only BUILTIN\Admins can use SSMS. Anyting special
>> >> > that
>> >> > must
>> >> > be
>> >> > done to open up the SSMS to Reporting Services for non
>> >> > BUILTIN\Admins?
>> >>
>> >>
>> >>
>>