Page Comparison

...

SQL to Restart the Object Creation

Both Databases
- drop table mv_directory_person

SQL Server
- delete from databasechangelog where filename = 'org/jasig/ssp/database/changesets/000130.xml' and id = 'update for new installs directory_person view'
- delete from databasechangelog where filename = 'org/jasig/ssp/database/changesets/000130.xml' and id = 'create mv directory_person view and pop msql'
PostgreSQL
- delete from databasechangelog where filename = 'org/jasig/ssp/database/changesets/000130.xml' and id = 'create mv directory_person view and pop postgresql'

4) To support the new person directory described above, stored procedures (SP) were created to execute large database operations.  Following each create statement, there is a statement to grant permissions to execute the SP included in the 2.5.1 release.  For SQL Server implementations, the grant statement may fail for certain account roles/permissions combinations.  Executing the grant statements independently is highly recommended.  The statements below cover the four new SPs and must be adjusted to replace 'ssp' with the db_username in the ssp-config.properties file.

GRANT EXEC on dbo.REFRESH_MV_DIRECTORY_PERSON to ssp;

GRANT EXEC on dbo.REFRESH_MV_DIRECTORY_PERSON_BLUE to ssp;

GRANT EXEC on dbo.update_directory_person_from_view_where_school_id to ssp;

GRANT EXEC on dbo.update_directory_person_from_view_where_person_id to ssp;

5) A change noted in the external data definitions for v2.5.X may affect the initial deployment.  A change was made to external_student_transcript_course.grade to make the column non-nullable.  As the database changes are made during deployment, the application will fail if any of the rows contains a null grade.  To correct the problem update the rows to ensure grade is not null and restart the application.  Some implementers do not generally record grades for current and future terms.  Those implementers that don't commonly use 'IP' for the current term and 'RG' for future terms.  Any grade can be used as long as it's not null.

56) SSP -2035 moved configuration items from a javascript file, Configuration.js, to the config database table.  This will allow SSP administrators to make all functional configuration changes in the user interface.  The changes are noted in the Configuration Guide, and the entire guide should be reviewed for new configuration items.  Upon deployment, the following configuration items should be made in the user interface to retain configurations previously made in Configuration.js.

...