Workaround for Mis-scheduling Caused By Daylight Saving Issue

From support-works
Revision as of 14:02, 23 August 2016 by Deenc (talk | contribs) (Created page with "'''Workaround for Mis-scheduling Caused By Daylight Saving Issue''' '''Problem''' There is an issue whereby Supportworks tasks, calls and reports scheduled prior to a daylig...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Workaround for Mis-scheduling Caused By Daylight Saving Issue

Problem

There is an issue whereby Supportworks tasks, calls and reports scheduled prior to a daylight-saving clock-change trigger one hour earlier or later than expected after the change.

Solution The workaround for this issue entails following either of the procedures given below, depending on whether the clocks have moved forward or back.

If Clocks Have Moved Forward

1. Run the Interactive SQL utility supplied with Supportworks by selecting Start > All Programs > Hornbill Core Services > Interactive SQL. 2. In the command window, enter the following SQL statements:

use sw_systemdb;

update system_scheduledcalls set schtime = schtime - 3600;

update system_scheduledjobs set nexttime = nexttime - interval 1 hour;

exit

If Clocks Have Moved Back

1. Run the Interactive SQL utility supplied with Supportworks by selecting Start > All Programs > Hornbill Core Services > Interactive SQL. 2. In the command window, enter the following SQL statements:

use sw_systemdb;

update system_scheduledcalls set schtime = schtime + 3600;

update system_scheduledjobs set nexttime = nexttime + interval 1 hour;

exit