Want to get rid of Google Ads, click here.
+ Reply to Thread
Results 1 to 3 of 3

Thread: RDBMS clocks?

  1. #1
    Senior Member
    Join Date
    Jun 2002
    Location
    Texas
    Posts
    374

    Default RDBMS clocks?

    I've noticed this error when we export to SQL, but I am curious if it is present in other RDBMSs. When we export our data to SQL, all the times on any incident/call ticket gets pushed forward by 6 hours. What, if any, function controls this?

    The times displayed when in P4 are correct - the error only crops up on the SQL data.

  2. #2
    Member
    Join Date
    Jul 2002
    Location
    Florida, USA
    Posts
    56

    Default

    This is controlled by an sc.ini entry on your server. You need to specify what time zone to use to store the rdbms data. Here is the excerpt from the data admin guide:


    sqltz
    An optional parameter to control storing of date/time values in the
    RDBMS. This parameter tells the SQL Interface what timezone to use as
    a base for all date/time values. The timezone is specified as the name of
    the timezone record in the ServiceCenter tzfile. The default timezone is
    Greenwich/Universal (GMT).
    sqltz:tz_name
    • To have all date/times be stored based on the Pacific timezone,
    tz_name would be specified as US/Pacific. For example:
    sqltz:US/Pacific
    Shirley

  3. #3
    Senior Member
    Join Date
    Jun 2002
    Location
    Texas
    Posts
    374

    Default

    Ah good eye there...thanks for pointing that out for me.

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

     

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts