SchemaSpy Analysis of topp.junk - Anomalies

Generated by SchemaSpy

Things that might not be 'quite right' about your schema:

• Columns whose name and type imply a relationship to another table's primary key:
  Anomaly not detected

• Tables without indexes:

  Table	Rows
  atn_track_qc_bak	6,273
  b	4
  bar	0
  barbar	0
  baz	49
  bb	4
  bowhead	1
  c	5
  candidates	49
  changed_eseals	49
  dc	60
  dcs	60
  deleteme	30
  e	7,652
  eseal	78
  f	3
  foo	1
  g	4
  h	8
  hits	10
  id	1,849
  input	2
  lackys	7
  main	5
  match_rows	2
  metadata	25
  misc	76
  now_and_them	1
  sample	1
  satdeployments_bak	4,616
  saved_eseal_atn_track_qc	14
  sd	1
  sd_changes	49
  ssmupdates_bak	27,564
  starts	5
  tables	12
  target_ptt	49
  targets	49
  td	1
  test	1
  test_df	30
  testdata	1
  testdata2	1
  tmp	3
  turtle	1
  ut	15
  wc_whitesharks	2
  whaleshark	1
  whiteshark	2

  49 instances of anomaly detected

• Columns that are flagged as both 'nullable' and 'must be unique':
  Anomaly not detected

• Tables that contain a single column:

  Table	Column
  barbar	foo
  c	d
  changed_eseals	eventid
  eseal	eventid
  g	x
  h	x
  hits	t
  id	eventid
  lackys	table_name
  misc	eventid
  target_ptt	pttnumber
  targets	eventid

  12 instances of anomaly detected

• Tables with incrementing column names, potentially indicating denormalization:

  Table
  whiteshark

  1 instance of anomaly detected

• Columns whose default value is the word 'NULL' or 'null', but the SQL NULL value may have been intended:
  Anomaly not detected