Changes coming to Polaris Reports
Updated June 6
All applicable staff client reports have been updated. For reference, see the full list of reports that will remain on production (tab 1), along with a list of all reports that will run against the reports database (tab 2). No changes will be made to Simply Reports this week, and these changes will not affect CCS's web reports.
Updated June 4
This work has been delayed. The first batch of reports will be updated tomorrow, June 5, before 9 AM.
Updated June 3
Cataloging and Circulation Staff Client Reports Updating June 4
Innovative staff will be updating staff client reports found in the Cataloging and Circulation folders and subfolders tomorrow before 9 AM Central. Only reports that will use report server data will be updated. We will confirm via system-status when that work is compete.
The remaining reports that will use reports data will be moved on Wednesday, June 5 before 9 AM.
For reference, see the full list of reports that will remain on production (tab 1), along with a list of all reports that will run against the reports database (tab 2). No changes will be made to Simply Reports this week, and these changes will not affect CCS's web reports.
Library staff will continue to access reports in the same place, following the same steps. Data will be current as of the previous night for all reports using reports server data.
Updated May 31
First Change to Polaris Reports Coming Next Week
Next week, Innovative will begin making changes to our report configuration. These changes will alleviate some of the load on the production database and ensure that resource intensive reporting does not impact day-to-day operations. The updates will be done in two parts.
Part 1: Tuesday, June 4 to Wednesday, June 5
Innovative will reconfigure the majority of the canned reports in the staff client to run against a copy of the database stored on our reports server. Moving forward, the reports database will be updated nightly with a copy of our production database.
CCS has identified a number of reports that require up to the minute information, such as notices and the picklist. They will continue to run against our live production database. Attached is a full list of reports that will remain on production (tab 1), along with a list of all reports that will run against the reports database (tab 2).
Innovative will be manually updating each report to redirect to the reports server, and the work could take several hours. It will not require any Polaris or staff client downtime, but individual reports may be inaccessible for a brief period (less than five minutes) while they are being redirected. CCS will meet with Innovative staff on Monday, June 3 to review their work plan, and will send additional details after that call. Again, notices, the picklist, and other reports that will remain on production will not be impacted.
Part 2: Week of June 11 (anticipated)
The next phase of the project is reconfiguring Simply Reports. Innovative is completing additional testing, and CCS will share more information on this second change as soon as it becomes available.
What affect will this have on my reports?
Data in most reports will be current as of the previous night, 11:00 PM. The timing was mandated by the overnight processes schedule, which must kick off at midnight. The production backup, which becomes the reports database, must be made prior to those jobs starting.
Where it is important to have up to the minute data, such as notices, data will continue to be pulled directly from the production database.
How will I know where my data is coming from?
The system will be configured to pull data from the correct database, with no special action needed by library staff. CCS and Innovative have documented which reports will pull production data (up to the minute) and which will pull reports data (from the previous night). Full report list
Will I have to log in to a new interface?
No, you will continue to use your Polaris username and password to access SimplyReports and the staff client as needed.
What if I need current, day-of data to correct an error or investigate an issue for a patron?
Some reports will still pull current data. CCS and Innovative will be refining system procedures and provide a list of reports that will continue to access production data prior to making this change.
Why is this change happening now?
Innovative is continuing to monitor and analyze our servers to completely resolve any performance issues. In at least two cases in recent months, we saw a slow down in system performance due to SimplyReports processes. This change will prevent similar issues in the future.
Previously shared: May 17, 2019
Over the next two weeks, Innovative will be reconfiguring our existing Polaris report server. We don’t expect downtime during library hours as a result of this project, and anticipate the changes will be live on May 28.
Currently, the report server manages the SimplyReports interface, schedule, and related services. When reports are run, the report server requests the relevant data from the production database. This means that during periods of intense reporting, we could see a slowdown in the staff client, Leap, or PowerPAC.
We will be creating a copy of the production database which will be used for most reports. Moving forward, we’ll refer to it as the report database. The report database will be stored on the report server and will be updated nightly. Most SimplyReports or staff client Reports (found in Utilities) will be run against the new report database when the project is complete.
This change will alleviate some of the load on the production database and ensure that resource intensive reporting does not impact day-to-day operations.