Ad Widget

Collapse

SQL schema and unicity on history/history_uint

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dakol
    Member
    • Jan 2008
    • 50

    #1

    SQL schema and unicity on history/history_uint

    there is one index on histories tables:

    CREATE INDEX history_1 on history (itemid,clock);
    CREATE INDEX history_uint_1 on history_uint (itemid,clock);

    Question:

    Why this index is not unique ?

    Is it expected to have more than 1 value for each (itemid, clock) ?
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    Originally posted by dakol
    Is it expected to have more than 1 value for each (itemid, clock) ?
    Why not? SNMP traps, for example.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    • dakol
      Member
      • Jan 2008
      • 50

      #3
      Originally posted by Alexei
      Why not? SNMP traps, for example.
      1 item belongs to 1 host, how a host could send 2 values at the same time ?

      link up/down ?

      perhaps clock might be more precise ? milliseconds ?

      Comment

      Working...