SchemaSpy - shrdb.LAWSN

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:

Child Column	Implied Parent Column
EMAILHISTORY.GUIDKEY	TMP_EMAILHISTORY.GUIDKEY
ENPSYSTEMPERMISSIONS.SYSTEMTASKID	ENPSYSTEMTASKS.SYSTEMTASKID
QRTZ_FIRED_TRIGGERS.INSTANCE_NAME	QRTZ_SCHEDULER_STATE.INSTANCE_NAME
QRTZ_FIRED_TRIGGERS.TRIGGER_GROUP	QRTZ_PAUSED_TRIGGER_GRPS.TRIGGER_GROUP
QRTZ_TRIGGERS.CALENDAR_NAME	QRTZ_CALENDARS.CALENDAR_NAME
QRTZ_TRIGGERS.TRIGGER_GROUP	QRTZ_PAUSED_TRIGGER_GRPS.TRIGGER_GROUP

6 instances of anomaly detected

Tables without indexes:

Table Rows

SNAUDIT 0

1 instance of anomaly detected
Columns that are flagged as both 'nullable' and 'must be unique':

Column

ENPBATREE.HIERARCHY

ENPCATEGORIES.CATEGORYDESC

ENPENTRYACCESSTYPES.ACCESSTYPEDESC

ENPLOGSOURCES.LOGSOURCEDESC

4 instances of anomaly detected
Tables that contain a single column:

Table Column

ENPCATLISTHELPER CATEGORYID

ENPREFLISTVIEW TREEENTRYID

QRTZ_LOCKS LOCK_NAME

QRTZ_PAUSED_TRIGGER_GRPS TRIGGER_GROUP

4 instances of anomaly detected

Table	Rows
SNAUDIT	0

Column
ENPBATREE.HIERARCHY
ENPCATEGORIES.CATEGORYDESC
ENPENTRYACCESSTYPES.ACCESSTYPEDESC
ENPLOGSOURCES.LOGSOURCEDESC

Tables with incrementing column names, potentially indicating denormalization:

78 instances 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