SchemaSpy Analysis of db176 - Anomalies

Generated by SchemaSpy

Things that might not be 'quite right' about your schema:	Please support this project

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

  Child Column	Implied Parent Column
  account_activity.PERSONNEL_ID	personnel.PERSONNEL_ID
  account_state.PRD_TYPE_ID	prd_type.PRD_TYPE_ID
  client_perf_history.ID	loan_arrears_aging.ID
  coll_sheet_customer.COLL_SHEET_ID	coll_sheet.COLL_SHEET_ID
  coll_sheet_loan_details.COLL_SHEET_CUST_ID	coll_sheet_customer.COLL_SHEET_CUST_ID
  customer_attendance.ID	loan_arrears_aging.ID
  customer_hierarchy.HIERARCHY_ID	personnel_hierarchy.HIERARCHY_ID
  customer_level.LEVEL_ID	personnel_level.LEVEL_ID
  customer_note.COMMENT_ID	personnel_notes.COMMENT_ID
  customer_position.POSITION_ID	position.POSITION_ID
  customer_schedule.ID	loan_arrears_aging.ID
  customer_state.STATUS_ID	office_status.STATUS_ID
  customer_state_flag.FLAG_ID	account_state_flag.FLAG_ID
  fee_frequency_type.FEE_FREQUENCY_ID	fee_frequency.FEE_FREQUENCY_ID
  fee_status.STATUS_ID	office_status.STATUS_ID
  feelevel.LEVEL_ID	personnel_level.LEVEL_ID
  fees.FEE_PAYMENTS_CATEGORY_TYPE_ID	fee_payments_categories_type.FEE_PAYMENTS_CATEGORY_TYPE_ID
  group_perf_history.ID	loan_arrears_aging.ID
  loan_activity_details.ID	loan_arrears_aging.ID
  loan_fee_schedule.ACCOUNT_FEES_DETAIL_ID	customer_fee_schedule.ACCOUNT_FEES_DETAIL_ID
  loan_perf_history.ID	loan_arrears_aging.ID
  loan_schedule.ID	loan_arrears_aging.ID
  mis_bankbranch.areaid	mis_geographicalarea.areaid
  mis_bankbranch.bankid	mis_bank.bankid
  mis_geographicalarea.areatypeid	mis_geographicalareatype.areatypeid
  mis_shgmemberprofile.groupid	mis_shgprofile.groupid
  mis_shgprofile.areaid	mis_geographicalarea.areaid
  mis_shgprofile.bankbranchid	mis_bankbranch.bankbranchid
  office_custom_field.FIELD_ID	custom_field_definition.FIELD_ID
  office_hierarchy.HIERARCHY_ID	personnel_hierarchy.HIERARCHY_ID
  office_level.LEVEL_ID	personnel_level.LEVEL_ID
  prd_category.OFFICE_ID	office.OFFICE_ID
  report.ACTIVITY_ID	activity.ACTIVITY_ID
  report.REPORT_ID	report_jasper_map.REPORT_ID
  report_category.ACTIVITY_ID	activity.ACTIVITY_ID
  report_parameter.DATASOURCE_ID	report_datasource.DATASOURCE_ID
  report_parameter_map.PARAMETER_ID	report_parameter.PARAMETER_ID
  saving_schedule.ID	loan_arrears_aging.ID
  savings_activity_details.ID	loan_arrears_aging.ID
  savings_performance.ID	loan_arrears_aging.ID

  40 instances of anomaly detected

• Tables without indexes:

  Table	Rows
  database_version	1

  1 instance of anomaly detected

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

  Column
  account.GLOBAL_ACCOUNT_NUM
  customer.GLOBAL_CUST_NUM
  fees.GLOBAL_FEE_NUM
  personnel.GLOBAL_PERSONNEL_NUM
  personnel.SEARCH_ID

  5 instances of anomaly detected

• Tables that contain a single column:

  Table	Column
  customer_account	ACCOUNT_ID
  database_version	DATABASE_VERSION
  insurance_offering	PRD_OFFERING_ID

  3 instances of anomaly detected

• Tables with incrementing column names, potentially indicating denormalization:

  Table
  customer_address_detail
  mis_shgprofile
  office_address
  personnel_details

  4 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