Data Impacting Performance Block

Important

Information and features vary according to the roles to which you belong and the permissions associated with those roles. For more information, contact your module manager or your campus support team.

This block identifies data issues that are impacting overall system performance. Issues are listed in order of importance. Click Refresh to see an updated list of issues.

Common Performance Issues

Building Codes with Multiple Locations

A previously released version of EX allowed the same Building Code to be used on multiple buildings (Room Master window) when the code should represent only one building. This issue was resolved in the 7.1 release, but the incorrect data remains and impacts J1 Web system performance. It also means buildings and rooms associated with duplicated codes were not synchronized to J1 Web Facilities.

Note

This issue only impacts clients that had EX version 7.1 or earlier installed.

Run the Jenzabar-provided query to identify buildings using overlapping building codes.

WITH distBldg (BLDG_CDE, LOC_CDE) AS
       (
       SELECT DISTINCT BLDG_CDE, LOC_CDE
         FROM ROOM_MASTER
       ),
       dupBldg (BLDG_CDE) AS
       (
       SELECT BLDG_CDE
         FROM distBldg
        GROUP BY BLDG_CDE
        HAVING COUNT(*) > 1
       )
SELECT rm.BLDG_CDE, rm.LOC_CDE
  FROM distBldg rm
  JOIN dupBldg d ON rm.BLDG_CDE = d.BLDG_CDE;
go

Create separate Building Codes for each location.
Update the Room Master data to use the correct building codes manually or using Jenzabar-provided stored procedures.
Ensure your school has installed the 7.1 release. The 7.1 DSU converts the corrected rows into Facilities using the corrected Building\Room Master data, if possible.
To manually convert this data, execute the following stored procedures in the exact order shown:
Caution
For a successful conversion, both must be executed in the specified order.
```
EXEC EXi_CONVERT_BUILDING_MASTER;
EXEC EXi_CONVERT_ROOM_MASTER;
go
```

Improper Microsoft SQL Server Max Memory Configuration

Performance is impacted when the Microsoft SQL Server Max Memory configuration is left at the 2,147,483,647 MB default. Jenzabar recommends making this value 75 – 90% of the available sever memory.

To resolve the issue, follow the steps provided in Microsoft's Server Memory Configuration Options article: https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed.

Number of Students Actively Pursuing Degrees

Performance is impacted when graduated and former students remain active/current in the system. Jenzabar provides a script to help evaluate the active/open rows in the Degree History table letting you identify and deactivate graduate and former students.

Run the EXiPermissionsChange script below while the system is running. The EXiPermissionsChange stored procedure evaluate rows in degree_history marked active/open.

Warning

Because this script is executed while the system is running, performance is impacted. Jenzabar recommends running it during a less active time.

SELECT count(*) -- sm.ID_NUM, nmStudent.LAST_NAME, nmStudent.FIRST_NAME
  FROM STUDENT_MASTER sm
  JOIN DEGREE_HISTORY dh ON sm.ID_NUM = dh.ID_NUM AND dh.ACTIVE = 'Y' AND dh.DTE_DEGR_CONFERRED IS NULL
              AND dh.EXIT_DTE IS NULL AND dh.CUR_DEGREE = 'Y'
  JOIN NAME_MASTER nmStudent ON sm.ID_NUM = nmStudent.ID_NUM
  JOIN Person peStudent ON nmStudent.APPID = peStudent.NameMasterAppID
  JOIN Party paStudent ON peStudent.AppID = paStudent.AppID

Evaluate all the active/current students listed.
Deactivate graduated and former students.

Students Misidentified as Organizations

Performance is impacted when student names are identified as organizations and not person records.

Run the following query to identify those students incorrectly identified in the Organization table instead of the Person table.

SELECT sm.ID_NUM, nmStudent.LAST_NAME, nmStudent.FIRST_NAME, nmStudent.PARTY_TYPE
  FROM STUDENT_MASTER sm
  JOIN NAME_MASTER nmStudent ON sm.ID_NUM = nmStudent.ID_NUM
  JOIN Organization org ON nmStudent.APPID = org.NameMasterAppID
  JOIN Party paStudent ON org.AppID = paStudent.AppID

Update the identified students' record from 'O' to 'P' in the NAME_MASTER.PARTY_TYPE column.

Additional Data Issues

Department Chairs as Secondary Advisors

Several clients contracted with Jenzabar Services to implement custom code that made students’ Department Chairs their Advisor as well.

Employee Roster Incorrectly Setup

If Employee-Supervisor hierarchy is set up in J1 Desktop or J1 Web way that there is a circular reference, issues in J1 Employee occur.

Notice

Employee 111 supervises Employee 222. Employee 222 supervises Employee 333. Employee 333 gets set up to supervise Employee 111.

Section Schedules with Incorrect Begin/End Dates

Schools with incorrect begin/end dates defined in SECTION_SCHEDULES will have issues when adding those classes to the CalendarTimeslot table.

Notice

A school had a section that began Jan 1, 2000 and ended on May 5, 8029. The end year is a data entry mistake, but the system still tried to create 6,000 years' worth of timeslots.

Data Impacting Performance Block

Important

Common Performance Issues

Building Codes with Multiple Locations

Note

Caution

Improper Microsoft SQL Server Max Memory Configuration

Number of Students Actively Pursuing Degrees

Warning

Students Misidentified as Organizations

Additional Data Issues

Department Chairs as Secondary Advisors

Employee Roster Incorrectly Setup

Notice

Section Schedules with Incorrect Begin/End Dates

Notice

Related Topics

Search results