
Mayuresh12 asked a question.
Hi All, We recently setup SMTP and its running fine. But I have few questions:
1. Will the SMTP or Snow Database Server be Overloaded if multiple users scheduled multiple reports? If yes, how do we overcome this?
2. Is there any way to keep track on all the scheduled reports by all the users?
3.Is there a way to restrict some users from scheduling reports in SLM? we just want some users to have the ability to schedule the reports but not all of them?
Hi,
1. Will the SMTP or Snow Database Server be Overloaded if multiple users scheduled multiple reports? If yes, how do we overcome this?
In the event of an overload, the platform would have to be extremely busy. (more than 100,000 assets)
Here it would be advisable to have the report created in the cache in advance and then the reports are sent cleanly to the individual users via scheduler.
2. Is there any way to keep track on all the scheduled reports by all the users?
The Snow License Manager Report Exporter is responsible for this. You can evaluate which reports have been created in the log files on a daily basis: C:\Program Files\Snow Software\Logs\ReportExport
However, it is not really possible to trace which user belongs to which report in the log file.
3.Is there a way to restrict some users from scheduling reports in SLM? we just want some users to have the ability to schedule the reports but not all of them?
Unfortunately, there is no restriction on the rights role concept. Here you might have to resort to manual solutions that are not necessarily as practical.
Cheers
Lars
Thanks @Lars Reifegerste
Hi @Lars Reifegerste ,
One question:
If I cache a report, will the scheduled SMTP report be extracted from that cache or DB stored procedure for that report? If it is extracted from that cache, will it be applicable for all the users that schedule reports?
I have the admin access. And because only admin have the ability to cache a report our normal users will just schedule reports without caching it, so I need to cache it using my account but schedule it using there.