• It is required that the system is up to minimum System Requirements for the Snow application and SQL server. Please see the Snow System Requirements and Best Practices for Large Environments.
• Please also see this article regarding report caching if you use SNow License Manager 9.13 or higher  https://community.flexera.com/s/article/Understanding-Cached-Reporting-in-Snow-License-Manager-9-13

After verifying that System Requirements are as required there are several recommendations that would be considered best practices for running reports and getting good tool performance:

• Consider how many rows would be returned in a report. Reports like 'Applications per computer', 'Applications per device', 'Applications per user', and 'Application installation history' can return results in the multiple millions of rows depending on the size of the environment and how long it has been up and running.
  • By design Snow License Manager limits reports to 1,048,576 rows as this is the hard limit set by Microsoft for Excel 2007 and after see Excel specifications and limits. This is also done for performance reasons.
  • For the larger reports you should set some Criteria for the report to limit the results to ensure it falls into the supported export ranges. Consider filtering based upon Application Manufacturer, Operating system, Portable computer, Server, etc. Try to ensure that report results are results limited to a data set that can be exported and viewed in Excel, and that is human readable. 
  • Make a point to think about the specific results you want from a report. You can filter easily in Snow License Manager to retrieve a data set that will make sense for whatever purpose you are trying to accomplish. Running a report that is more than a million rows is too much data to work in efficiently so limit it to a subset that serves the business need that is required.
• In addition to setting criteria to limit the report data set results reports can be scheduled to be emailed (if configured) or dropped to a drive or fileshare to be retrieved.
  • This is recommended for larger reports as it is a separate service that renders the reports in this way.
  • This means that the Web GUI performance should not be impacted while exporting the report. 
• You can also use the 'Export to file' option to run the report in the background instead of in the Web GUI. The report can then be retrieved from the 'Report files' section of the Reports page. Screenshot is attached below.