Si_Configurations Table Update Scripts

The GetStudentLifecycleHistory WCF service requires the following data manipulation language (DML) scripts to be run to update the Si_Configurations table:

• Cst_Si_Configurations_Update_Values_GetStudLifeCycle_Status.sql

  This script updates the Values column in the Si_Configurations table with comma-separated School Codes .

• Cst_Si_Configurations_Update_Values_GetStudLifeCycle_VendorCheckBypassUsers.sql

  This script updates the Values column in the Si_Configurations table with comma-separated Staff Codes.

  Download .zip file containing the scripts:

  

To run the scripts

1. Open Microsoft SQL Server Management Studio.

2. Open the DML script file in SQL Server Management Studio.

3. Enter the value(s) as a comma-separated list in the variable @data.

   Note: Specify the value(s) within the single quotes.

   Example

   In the script, the value(s) are currently indicated as follows:

   set @data = ''

   To populate the @data, refer to the following sample query for the script:

   Cst_Si_Configurations_Update_Values_GetStudLifeCycle_Status –
      select @data = COALESCE(@data + ',' + 
      convert(varchar,ltrim(rtrim(SySchoolStatus.Code))), 
      convert(varchar,ltrim(rtrim(SySchoolStatus.Code))))
           from dbo.SyStatus(nolock)
                inner join dbo.SySchoolStatus (nolock)
                on SySchoolStatus.syStatusID = SyStatus.syStatusID
                where SyStatus.Category = '<put your category here>''
                and SySchoolStatus.Active = 1
                order by SySchoolStatus.code

4. Apply the DML to the database.

    

FAQs

1. Is the update version specific?

   Yes, the update applies to CampusNexus Student 15.1 and higher.

2. Will the DML scripts need to be reapplied after a CampusNexus Student upgrade is done?

   Yes, they can be reapplied after the upgrade. It depends upon the implementation.

3. If so, in what version will there no longer be a need to run this update?

   These DML scripts are reapplied on a need basis.

4. Do users need to log off before running the update?

   No.

5. Does this update modify a stored procedure (or other)?

   Yes, it modifies the value in Si_Configuration table.

6. Does it matter how many times you run this update

   No.