We’ve made a lot of cool changes to the New Year Rollover process this year! In fact, it’s hard to list them all! You can read all about it in our documentation linked at the bottom of the article, but we’re going to highlight some of the more significant enhancements below.
The New Year Rollover now includes a new option to Lockout All Users during the rollover process. This option will not kick-out users already logged into Aeries, but it will keep users from logging in while the rollover is running.
When this “Lockout All Users” option is checked, users attempting to log into Aeries will see this message:
A new option has been added called “Copy custom SQL modules” (ROL.CCS). Checking this option will copy custom SQL modules such as views, functions, stored procedures, and triggers for customers who have extensively customized their Aeries SQL database.
For Custom Tables and Views defined in the “Define Custom Tables” form (CTD table), the SQL Table definition, Indexes, Constraints, Triggers, and Extended Properties will be created in the new year database prior to copying the data. When paired with the “Copy custom SQL modules” option above, this means that the Database Administrator will only need to run SQLMODEL.SQL on a newly created Aeries database for rollover!
Curious about the “PGMS” custom SQL view defined above? Click here
The Processes tab now includes a new AdminCS Maintenance Functions* summary of last run dates for: Repair Indexes and Relationships, Force Cascading DEL Tags, and Database Cleanup. The dates will be shown in red if it has been more than one week since they were last run. If you see a red date, be sure to run that function in AdminCS prior to starting the rollover.
Please note that this section will not be visible to our hosted clients.
A lot of new features have been added to make sure that cleaner data is rolled over. New Year Rollover will now automatically run “Force Cascading Del Tags” in order to ensure no orphaned records exist prior to the rollover. The process will now also ensure that teacher zero (“Unassigned”) exists at all schools, recalculate SMS Totals for secondary schools, bypass copying expired substitute teacher accounts, clean up portal accounts, and clear out data in Supplemental Attendance Session Linked MST Section (ATS.MSE). These steps reduce the amount of “Post-Rollover Cleanup” Aeries Admins used to do.
In order to better serve our K-8 customers, the existing “Only copy Student (STU) records under 25 years of age” has been modified to allow a user-defined age (ROL.UWA), defaulting to 25. Now districts can enter an age that is more appropriate for the communities they serve.
These are just a handful of the recent enhancements to the New Year Rollover process. Visit our support site for more information!\n\n
- New Year Rollover Overview
- New Year Rollover Checklist (Updated May 22nd, 2018)
- New Year Rollover Settings
- New Year Rollover Processing and Reports
- Pre-Rollover Audit Listing Report