Skip to main content

Show permissions on all SSRS folders

Here is a useful (if rather verbose) script that will show users and their permissions from the root folder on SQL Server Reporting Services downwards. It should work on most if not all versions of the product. You can use it as is, or as a starting point to create your own aggregations etc.

USE ReportServer;

SELECT
CASE
              WHEN (SubString(c.[Path], 1, Len(c.[Path]) - (CharIndex('/', Reverse(c.[Path])) - 1))) = ''
                     THEN '<root folder>'
              ELSE SubString(c.[Path], 1, Len(c.[Path]) - (CharIndex('/', Reverse(c.[Path])) - 1))
              END AS Folder
       ,CASE
              WHEN c.Type = 1
                     THEN 'Path'
              WHEN c.Type = 2
                     THEN 'Report'
              WHEN c.Type = 3
                     THEN 'Resource'
              WHEN c.Type = 4
                     THEN 'Linked Report'
              WHEN c.Type = 5
                     THEN 'Data Source'
              WHEN c.Type = 6
                     THEN 'Report Model'
              WHEN c.Type = 7
                     THEN 'Report Part'
              WHEN c.Type = 8
                     THEN 'Shared Dataset'
              END AS 'ObjectType'
       ,CASE
              WHEN c.NAME = ''
                     THEN '<root folder>'
              ELSE c.NAME
              END AS ObjectName
       ,u.UserName
       ,r.RoleName AS [Permissions]
FROM [users] u
INNER JOIN PolicyUserRole pu
       ON u.userid = pu.userid
INNER JOIN roles r
       ON pu.roleid = r.roleid
INNER JOIN CATALOG c
       ON pu.PolicyID = c.PolicyID
ORDER BY c.NAME
       ,u.UserName


<end>

Comments

Popular posts from this blog

How to create a custom Windows Event Log view and email trigger

The filtering on Windows event logs can be slow, clunky and although you can do it on fields like event ID, it seems that many event IDs are shared amongst many different errors – the event ID may match but the body of the error (therefore the actual error) may be completely unrelated. Fortunately, it is possible to filter on the contents of the body of the error message but it requires creating a custom XML query. Also, it would be handy to send out a notification email when this event gets logged. Read on to find out how to work this magic…. This example is looking for a  Warning  event  1309  for  ASP.NET 4.0.30319.0  on a web server. If you were to just filter the log on the criteria above today it would return 435 results because it is a fairly general error ID. If I filter it using XML for SqlException (what I’m really interested in) only 5 results are returned. So the first step is go to the Application Log and choose  Create Custom View…  Select the  XML  tab, check  Edit

How to configure the SSAS service to use a Domain Account

NB Updating SPNs in AD is not for the faint hearted plus I got inconsistent results from different servers. Do so at your own risk! If you need the SSAS account on a SQL Server to use a domain account rather than the local “virtual” account “NT Service\MSSQLServerOLAPService”. You may think you just give the account login permissions to the server, perhaps give it sysadmin SQL permissions too. However, if you try and connect to SSAS  remotely  you may get this error: Authentication failed. (Microsoft.AnalysisService.AdomdClient) The target principal name is incorrect (Microsoft.AnalysisService.AdomdClient) From Microsoft: “A Service Principle Name (SPN) uniquely identifies a service instance in an Active Directory domain when Kerberos is used to mutually authenticate client and service identities. An SPN is associated with the logon account under which the service instance runs. For client applications connecting to Analysis Services via Kerberos authentication, th

How to import a large xml file into SQL Server

(Or how to import the StackOverflow database into SQL Server) Introduction NB  This process can be generalised to import any large (>2G) xml file into SQL Server. Some SQL Server training you can find online including that by Brent Ozar uses the StackOverflow database for practice. The tables from it are available online for download in xml format. In the past it was possible to use the scripts found here, https://www.toadworld.com/platforms/sql-server/w/wiki/9466.how-to-import-the-stackoverflow-xml-into-sql-server , to import them but as each xml file is now over 2GB you will get an error like this when you try to execute them: Brent Ozar, has a link to SODDI.exe, https://github.com/BrentOzarULTD/soddi , which can import the files (I haven’t tried it) but it means downloading and importing eight tables: Badges, Comments, PostHistory, PostLinks, Posts, Tags, Users, and Votes tables which amounts to >30GB of compressed xml increasing to ~200GB when decompre