Inverno asked a question.
Hello. SLM user here.
Some users were creating reports and sharing them with everybody (who knows why).
I just want to know who created the reports to contact them and unshare.
Is there any query that can give me the report name + creator name?
SLM on prem.
Thank you in advance
[dbo].[tblSystemUserReportShared] This table contains;
[ReportID]
[OwnerUserID]
[SharedUserID]
From this you can look up the user ID in tbluser and determine who is sharing the reports.
If you need the Report name what will be in tblReports and link the Report ID back to the Report name
Good day, @Inverno​
Hope you are doing well.
Give below SQL query a try, hopefully that helps. That will give the Report Name, along with the user who created the report with their First Name, Last Name and Email.
Select a.CID, a.ReportID, a.ReportName, a.Description, b.UserName, b.FirstName, b.LastName, b.Email from SnowLicenseManager.dbo.tblSystemUserReports a
join SnowLicenseManager.dbo.tblsystemuser b on a.UserID = b.UserID
Kind regards,
Randy Teng
Super useful guys. I am now able to contact the report owners to unshare. Really glad.
It's sad the support could not come to this level in this case. They just told me once shared it's not posible to delete.
Thank you all for the help here.
Support is in general really good at resolving factual errors, but they are focusing on actual errors. If it's something that is not really a defect, then they tend to brush that aside.
I don't know how you formulated yourself, but in general be very clear that you have an actual functional impact (in this case, it sounds like wantonly shared reports is not a big problem ... ? )
Having said all that - I would encourage you to browse around in the SnowInventory and SnowLicenseManager databases. I don't mean that you should become an expert xD But you can actually do quite a lot of analysis on your own. And if you're stuck, throw out a question here in the community :)
@Jonas_A_Nilsson​ really helpful context, appreciate you sharing your approach🙌
In this case it was getting people annoyed, even though it was not related to anything breaking or stop working. Imagine you have a dedicated report used by top management and internal auditors to control specific installations. In a matter of days, you ended up having 6+ equal reports on the same group, plus slighly different names, according to site or region report creators.
Although no functionality was impacted, the rapid proliferation of duplicate reports raised concerns about the tool’s ease of management.
Glad all worked out well.
Good point and that's actually a useful framing for future support interactions.
Sometimes a problem that looks on the surface to have mild impact - or perhaps no impact at all - but in reality, it not only looks untidy, but is also unexplainable and clumsy - then it undermines the confidence in the system, so it is good to lead with that, or articulate it explicitly. Imagine if a bank suddenly were to send out 10 copies of your bank statement, and then just waved it away...?
As others have said above, SLM and Snow Inventory databases are quite readable once you get a feel for the schema. You don't need to become an expert, but being able to formulate your own queries - or at least know what questions to ask here - gives you a lot more leverage than waiting for support to engage.
Glad the community could fill that gap this time.
Good day, @Inverno​
Hope you are doing well.
Give below SQL query a try, hopefully that helps. That will give the Report Name, along with the user who created the report with their First Name, Last Name and Email.
Select a.CID, a.ReportID, a.ReportName, a.Description, b.UserName, b.FirstName, b.LastName, b.Email from SnowLicenseManager.dbo.tblSystemUserReports a
join SnowLicenseManager.dbo.tblsystemuser b on a.UserID = b.UserID
Kind regards,
Randy Teng