The New Year Rollover page is in the Navigation menu under School Info | Functions. There are 3 tabs on the New Year Rollover page: Settings, School Based Fields and Processes

The Settings tab includes District Wide, Inactive School and School Based settings, with the option to push one school's settings to selected schools. The School Based settings can be viewed at either the School or District to easily set up the defaults and push the School Based settings to other schools. The District Wide settings will not display unless viewing the District School Code. All the settings are stored in the Rollover Settings (ROL) table that will roll forward to the new year. 




The School Based Fields tab shows which COD table fields have been designated as School-based. This information can be exported to Excel.

The Processes tab includes four categories: Admin CS, Pre-Rollover, Rollover, and Post-Rollover

The AdminCS section shows the last time Maintenance functions were run.

The Pre-Rollover section includes reports to be run prior to the rollover: Pre-Rollover Audit Listing, and Table Record Counts (Pre)

The Rollover section includes details on how to setup the rollover, and a button to Start Rollover

The Post-Rollover section includes reports to be run upon completion of the rollover: Missing Students Report, and Table Record Counts (Post).


The New Year Rollover page can be found under School Info | Functions in the Navigation Menu. Security to access this page can be granted under the School Information | New Year Rollover area of the Permissions page.

User accounts with Read access to the New Year Rollover can view the Settings, School Based Fields tabs and run the reports in the Processes tab.

User accounts with Update access to the New Year Rollover can view and update the information in the Settings tab and also push the settings to other schools. These users can also run the reports in the Processes tab.

Only Admin accounts have full access to the New Year Rollover. Admins can view and edit the Settings tab and push the settings to other schools, run the reports in the Processes tab, and initiate the Rollover.

Note: For Hosted customers, only Aeries support staff can edit the Settings and initiate the Rollover.

For more information on how to set up security please refer to the Aeries Security documentation.

New Year Rollover Requirements

The New Year Rollover in Aeries Web Version is initiated from the current year database and rolled from the current year database into the new year database. It is very important that the most recent updates of both the Aeries Web Version and the Aeries Client Version are utilized. Prior to running the New Year Rollover process, the new year database needs to be created in SQL Server Management Studio. The new year database must have the same Database Suffix as the current year database with the year increased by one (for example DST22000EagleUSD). The most recent SQLModel database structure can be downloaded by clicking on the Download SQLModel.sql button. Once downloaded it needs to be run against the new database to create the table structure.

The New Year Rollover process requires the website to be accessed via HTTPS. If HTTPS is not used a message will display in the Rollover section of the Processes tab indicating that the rollover must be run under HTTPS.

The administrator performing the rollover will also need to enter the DBO User Name and DBO Password to begin the rollover.

NOTE: This elevated SQL login is necessary because the rollover entails copying more than just data (e.g., security and some table definitions). At minimum, the login must be a member of the db_owner database role on both the current and new year databases and have the ALTER ANY LOGIN server-level permission. Using a login that is a member of the sysadmin fixed server role is one way to guarantee that permissions are adequate.

Data Verification

Prior to initiating the New Year Rollover, verification should be performed to ensure that the data will be copied over correctly.

Current Year Database Verification includes:

  • Run the utilities under Maintenance Functions on the Administrative Functions page on the current year database to help clean up the database prior to rollover – Repair Indexes and Relationships (currently in AdminCS), Force Cascading DEL Tags, Database Cleanup, LaunchFix ENR Process.
  • Review all CALPADS requirements for exiting students. (Refer to Aeries documentation topics including: Reporting Graduating Students to CALPADS, Reporting Matriculating Students to CALPADS, and CALPADS Student Withdrawal Data Population Guide). Students that have End of Year Status (STU.EOY) populated may also need to have the STU.ENS populated. Please refer to the CALPADS Student Withdrawal Data Population Guide for more information.

NOTE: The STU.ENS does not affect rollover; it is populated for CALPADS reporting.

  • Verify School Options Low and High Grade Ranges (LOC.LO and LOC.HI) for all schools and the district. Districts should not have the district high grade, stored in LOC.HI, be above 12 even if they are using higher grade levels for Special Ed, Adult Ed or other students. The District high grade of 12 ensures that the graduating seniors are dropped during the rollover. Please note that the only reason a school's high grade, stored in LOC.HI, should ever be above 12, is if the low grade is also above 12 (i.e., Adult Ed with grade-range of 15-15). Students with grade levels higher than 13 will roll with the same grade level during the rollover if the Do Not Bump Grade option is selected for that grade level; otherwise, they will roll with the grade level in the Next Grade (STU.NG) field.
  • Graduating Seniors should have a Next Grade of 13 to be copied into the Inactive School.
  • Verify ALL schools have set up their pre-enrolled students with the correct next grade and that there is an asterisk (*) in the STU.TG field.
  • Consider any changes that will need to be made to tables that are district owned such as the code table, course data, etc.
  • New schools need to be added to the current school year database, including any grade level changes.
  • Verify the Next School (STU.NS) field is populated with the school the students will be attending next year, even if the students are returning to the same school. The STU.NS can be populated with either the current school code if they are returning to the same school in the New Year database, the Next School code that they will be attending if they are moving to a different school within the district, or with the Inactive School code if they are leaving the district. If left blank, they will continue in the current school.

NOTE: the STU.NS field will determine which school the student will roll into during rollover.  Pre-enrolled students will roll into the school where the pre-enrolled record is created unless the option to Copy Pre-Enrolled Students from This School to their Next School is checked.  . Also, inactive students who are not active or pre-enrolled at another school will roll to the inactive school regardless of the Next School field, unless the rollover option to use the inactive school is disabled.

  • Verify that the Next Grade (STU.NG) field is increased by one from the current Grade field to ensure that the student will roll over properly (unless the student has been retained, is pre-enrolled, etc.). 
  • If an elementary student will be assigned a teacher for the upcoming school year, verify the Next Teacher (STU.NT) field. If the student will be assigned a track for the upcoming school year, verify the Next Track (STU.NTR) field.
  • If any of the following options will be used during the rollover, then the values stored in these fields will need to be verified:
Copy Next School of Residence to School of Residenceverify STU.NRS
Copy Next Inter/Intra-District to Inter/Intra-Districtverify STU.NIT and STU.NTD
Copy Next Attr Code and ResDist to Attr Code and ResDistverify STU.NIT and STU.NTD
Copy Next Program (s) to Program(s)verify STU.NSP, STU.NP1, STU.NP2
 Copy Next ADA Elig Code and Program(s) to ADA Elig Code and Program(s)
verify STU.NSP, STU.NP1, STU.NP2
Copy Next Grid Code to Grid Codeverify STU.NGC

  • Check Cumulative Credits for seniors and determine if they will need to be retained and still held in the 12th grade when rollover is complete.
  • Print the Pre-Rollover Audit Listing and the Table Record Counts (Pre) from the Pre-Rollover section of the Processes tab. Make any corrections necessary to minimize the errors on the Audit Listing.

New Year Database Set Up includes:

  • From SQL Server Management Studio create a new database for next year with the same suffix as the current year and increase the year by one. For example, DST22000EagleUSD.
  • Run the latest SQLMODEL.sql script (download the script by clicking on the Download SQLModel.sql button) against the new database to create the table structure. This procedure MUST be done prior to rollover.
  • Do NOT login to the new year database in AdminCS prior to running the Rollover in Web. Using the latest SQLMODEL.sql file is sufficient to create all the tables and other objects in the new year database.

NOTE: SQLMODEL.SQL will make all available tables in the new year database ID-based tables, which is a prerequisite for using the Rollover in Web.

The New Year Rollover is now run in the Aeries Web Version. The AdminCS version is no longer available; however, this new method drastically streamlines the rollover process in that all schools are rolled in one run of the rollover process, and it has been tested to work about 10 times faster than the AdminCS version.

IMPORTANT: For Aeries administrators accustomed to the Client version of the New Year Rollover, there are some fundamental differences that must be understood when transitioning to the Rollover in the Aeries Web Version.
  • The Web Rollover runs as a single, continuous process. District-wide options and school-based options for each school are configured and saved before starting the Rollover. There are no separate steps required for “regular” schools, “special” schools, and the Inactive School.
  • There is no “Update Student Data” process in the Web Rollover. In Client, it was possible to perform the Rollover before all data was finalized in the previous year database. Then, the Update Student Data process would sync any changed data to the new year database at a later date.
  • However, as the Web Rollover is an all-in-one process, it is crucial that all data be finalized as much as possible in the previous year before rolling over. Once the Rollover has completed and been verified, all users should immediately start using the new year database. Any changes subsequently made to data in the previous year must be manually updated in the new year.
Given the significant performance enhancements in the Web Rollover, Aeries does not anticipate this being a problem for customers. Scheduling the Rollover at an opportune time should pose much less challenge than before.